CVE-2018-10824 in the critical feed json
An issue was discovered on D-Link DWR-116 through 1.06, DIR-140L through 1.02, DIR-640L through 1.02, DWR-512 through 2.02, DWR-712 through…
published 8y ago modified 4mo ago also EUVD-2018-2893
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.5%
- EPSS 12.5% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered on D-Link DWR-116 through 1.06, DIR-140L through 1.02, DIR-640L through 1.02, DWR-512 through 2.02, DWR-712 through 2.02, DWR-912 through 2.02, DWR-921 through 2.02, and DWR-111 through 1.01 devices. The administrative password is stored in plaintext in the /tmp/csman/0 file. An attacker having a directory traversal (or LFI) can easily get full router access.
Is CVE-2018-10824 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-45677)
- Published
Exploit prediction
12.48% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45677 D-Link Routers - Plaintext Password webapps, 2018-10-12
- seclists.org https://seclists.org/fulldisclosure/2018/Oct/36 referenced PoC, tagged "exploit" by a source, unverified
- sploit.tech http://sploit.tech/2018/10/12/D-Link.html referenced PoC, tagged "exploit" by a source, unverified
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 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
References
-
seclists.org
/fulldisclosure/2018/Oct/36
mailing-list, exploit, third-party-advisory
-
sploit.tech
/2018/10/12/D-Link.html
exploit, third-party-advisory
Sources
- CVE List CVE-2018-10824
- NVD CVE-2018-10824
Fencer Intel 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.