| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in D-Link DIR-601 B1 2.02NA. This issue affects some unknown processing. This manipulation causes credentials management (User). This vulnerability appears as CVE-2018-5708. The attacker needs to be present on the local network. In addition, an exploit is available. It is advisable to implement restrictive firewalling.
Details
A vulnerability classified as problematic was found in D-Link DIR-601 B1 2.02NA (Router Operating System). Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a credentials management vulnerability (User). The CWE definition for the vulnerability is CWE-255. As an impact it is known to affect confidentiality. The summary by CVE is:
An issue was discovered on D-Link DIR-601 B1 2.02NA devices. Being on the same local network as, but being unauthenticated to, the administrator's panel, a user can obtain the admin username and cleartext password in the response (specifically, the configuration file restore_default), which is displayed in XML.
The bug was discovered 03/28/2018. The weakness was presented 03/30/2018 as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. This vulnerability is known as CVE-2018-5708 since 01/16/2018. The attack needs to be initiated within the local network. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $5k-$25k.
Proper firewalling of is able to address this issue.
The vulnerability is also documented in the vulnerability database at Exploit-DB (44388). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.dlink.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.0
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: UserClass: Credentials management / User
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
01/16/2018 🔍03/28/2018 🔍
03/30/2018 🔍
03/30/2018 🔍
03/31/2018 🔍
08/28/2024 🔍
Sources
Vendor: dlink.comAdvisory: seclists.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-5708 (🔍)
GCVE (CVE): GCVE-0-2018-5708
GCVE (VulDB): GCVE-100-115273
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/31/2018 09:50Updated: 08/28/2024 22:47
Changes: 03/31/2018 09:50 (61), 01/18/2020 15:10 (5), 08/28/2024 22:47 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.