CVE-2017-8415 json
An issue was discovered on D-Link DCS-1100 and DCS-1130 devices.
published 2019-07-02 7 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17367
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
An issue was discovered on D-Link DCS-1100 and DCS-1130 devices. The device has a custom telnet daemon as a part of the busybox and retrieves the password from the shadow file using the function getspnam at address 0x00053894. Then performs a crypt operation on the password retrieved from the user at address 0x000538E0 and performs a strcmp at address 0x00053908 to check if the password is correct or incorrect. However, the /etc/shadow file is a part of CRAM-FS filesystem which means that the user cannot change the password and hence a hardcoded hash in /etc/shadow is used to match the credentials provided by the user. This is a salted hash of the string "admin" and hence it acts as a password to the device which cannot be changed as the whole filesystem is read only.
Exploit prediction
3.93% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
seclists.org
/bugtraq/2019/Jun/8
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/153226/Dlink-DCS-1130-Command-Injection-CSRF-Stack-Overflow.html
third-party-advisory, vdb-entry
-
github.com
/ethanhunnt/IoT_vulnerabilities/blob/master/Dlink_DCS_1130_security.pdf
not-applicable, third-party-advisory
Sources
- CVE List CVE-2017-8415
- NVD CVE-2017-8415
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.