CVE-2020-19320 json
Buffer overflow vulnerability in DLINK 619L version B 2.06beta via the curTime parameter on login.
published 3y ago modified 4mo ago also EUVD-2020-11224
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
Buffer overflow vulnerability in DLINK 619L version B 2.06beta via the curTime parameter on login.
Is CVE-2020-19320 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 FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
1.06% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/hhhhu8045759/dlink-619l-buffer_overflow 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 |
Affected products
- d-link dir-619l
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
github.com
/hhhhu8045759/dlink-619l-buffer_overflow
exploit, third-party-advisory
-
dlink.com
/en/security-bulletin/
vendor-advisory
Sources
- CVE List CVE-2020-19320
- NVD CVE-2020-19320
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.