CVE-2018-12113 json
Core FTP LE version 2.2 Build 1921 is prone to a buffer overflow vulnerability that may result in a DoS or remote code execution via a PASV…
published 8y ago modified 4mo ago also EUVD-2018-4091
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.9%
- EPSS 6.9% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
Core FTP LE version 2.2 Build 1921 is prone to a buffer overflow vulnerability that may result in a DoS or remote code execution via a PASV response.
Is CVE-2018-12113 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 FencerExploit prediction
6.87% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gist.github.com https://gist.github.com/berkgoksel/e97b3f3b15e2f8293f649d4ebe6a6fc9 referenced PoC, tagged "exploit" by a source, unverified
- gist.github.com https://gist.github.com/berkgoksel/a654c8cb661c7a27a3f763dee92016aa referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/148383/Core-FTP-LE-2.2-Buffer-Overflow.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
gist.github.com
/berkgoksel/e97b3f3b15e2f8293f649d4ebe6a6fc9
exploit, third-party-advisory
-
gist.github.com
/berkgoksel/a654c8cb661c7a27a3f763dee92016aa
exploit, third-party-advisory
-
packetstormsecurity.com
/files/148383/Core-FTP-LE-2.2-Buffer-Overflow.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2018-12113
- NVD CVE-2018-12113
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.