| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Ring Video Doorbell and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Setup Handler. The manipulation leads to credentials management (IoT). This vulnerability is documented as CVE-2015-4400. It is possible to launch the attack on the physical device. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Ring Video Doorbell (the affected version unknown). This issue affects an unknown part of the component Setup Handler. The manipulation with an unknown input leads to a credentials management vulnerability (IoT). Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality. The summary by CVE is:
Ring (formerly DoorBot) video doorbells allow remote attackers to obtain sensitive information about the wireless network configuration by pressing the set up button and leveraging an API in the GainSpan Wi-Fi module.
The bug was discovered 05/10/2015. The weakness was released 02/06/2018 (Website). It is possible to read the advisory at blog.fortinet.com. The identification of this vulnerability is CVE-2015-4400 since 06/06/2015. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 1003 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 2.4
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.6
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: IoTClass: Credentials management / IoT
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/10/2015 🔍06/06/2015 🔍
02/06/2018 🔍
02/06/2018 🔍
02/07/2018 🔍
01/02/2020 🔍
Sources
Advisory: blog.fortinet.comStatus: Not defined
CVE: CVE-2015-4400 (🔍)
GCVE (CVE): GCVE-0-2015-4400
GCVE (VulDB): GCVE-100-112871
Entry
Created: 02/07/2018 08:24Updated: 01/02/2020 07:29
Changes: 02/07/2018 08:24 (56), 01/02/2020 07:29 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.