CVE-2011-5012 json
Heap-based buffer overflow in the Reflection FTP Client (rftpcom.dll 7.2.0.106 and possibly other versions), as used in Attachmate Reflecti…
published 2011-12-25 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4917
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.8%
- EPSS 7.8% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Heap-based buffer overflow in the Reflection FTP Client (rftpcom.dll 7.2.0.106 and possibly other versions), as used in Attachmate Reflection 2008, Reflection 2011 R1 before 15.3.2.569 and R1 SP1 before, Reflection 2011 R2 before 15.4.1.327, Reflection Windows Client 7.2 SP1 before hotfix 7.2.1186, and Reflection 14.1 SP1 before 14.1.1.206, allows remote FTP servers to execute arbitrary code via a long directory name in a response to a LIST command.
Timeline
- First public exploit (EDB-18119)
- Published
Exploit prediction
7.75% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-18119 Attachmate Reflection FTP Client - Heap Overflow dos, 2011-11-16
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/18119
exploit
-
secunia.com
/advisories/46879
third-party-advisory, vendor-advisory
- support.attachmate.com /techdocs/1708.html
- support.attachmate.com /techdocs/2502.html
- support.attachmate.com /techdocs/2288.html
-
osvdb.org
/77189
vdb-entry
-
securitytracker.com
/id?1026340
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/71330
vdb-entry
- protekresearchlab.com /index.php?option=com_content&view=article&id=29&Itemid=29
Sources
- CVE List CVE-2011-5012
- NVD CVE-2011-5012
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.