dbcve.org
ReflectionApplication · Attachmate

CVE-2011-5012

HIGH · 10.0 CVSS v2.0 Published 2011-12-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap-based buffer overflow in Attachmate Reflection FTP Client (rftpcom.dll) allows remote FTP servers to execute arbitrary code via a long directory name in LIST command responses. The vulnerability affects Reflection 2008, Reflection 2011 R1/R2, Reflection Windows Client 7.2 SP1, and Reflection 14.1 SP1 across multiple version ranges.

MitigationUpdate affected Reflection products to the patched versions (15.3.2.569+, 15.4.1.327+, 7.2.1186+, 14.1.1.206+) or apply vendor-supplied hotfixes. Consider restricting FTP server connections to trusted sources until patches are applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ReflectionApplication
Affected:= 7.2= 14.1
Reflection 2008Application
Affected:all versions
Reflection 2008r1Application
Affected:= sp1
Reflection 2008r2Application
Affected:all versions
Reflection 2011r1Application
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Attachmate Reflection product
    Check Add/Remove Programs or program files directory for Attachmate Reflection installations. Look for directories like 'Attachmate Reflection' or check registry at HKLM\SOFTWARE\Attachmate
    Affected if Any Reflection 2008, 2011 R1/R2, 7.2, or 14.1 version is installed
  2. Determine exact version number
    Open the Reflection application and go to Help > About, or check the version in the Windows registry under the installed product's key
    Affected if Version matches 7.2 (any build), 14.1 (any build), or any 2008/2008r1/2008r2/2011r1 release
  3. Locate the vulnerable FTP component
    Search for rftpcom.dll on the system - typically in the Reflection program directory (e.g., C:\Program Files\Attachmate\Reflection\)
    Affected if rftpcom.dll exists on the system, indicating the FTP client module is present
  4. Verify FTP client is in use or configured
    Check if FTP sessions are configured in Reflection, or examine recent FTP connection logs. The vulnerability triggers when the client processes a malicious LIST response
    Affected if FTP functionality has been used or configured - the client must connect to an FTP server for the flaw to trigger

A user is affected if they have any version of Reflection 2008, 2011 R1, 7.2, or 14.1 installed AND the rftpcom.dll FTP client component is present and used to connect to FTP servers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected Reflection products to the patched versions (15.3.2.569+, 15.4.1.327+, 7.2.1186+, 14.1.1.206+) or apply vendor-supplied hotfixes. Consider restricting FTP server connections to trusted sources until patches are applied.

Recommended fix High confidence

Reflection 2011 R1: 15.3.2.569+ | Reflection 2011 R2: 15.4.1.327+ | Reflection 7.2 SP1: hotfix 7.2.1186+ | Reflection 14.1 SP1: 14.1.1.206+

  1. Identify the specific Reflection product and version currently installed (Reflection 7.2, 14.1, 2008, 2008r1, 2008r2, or 2011r1)
  2. For Reflection 2011 R1: Upgrade to version 15.3.2.569 or later
  3. For Reflection 2011 R2: Upgrade to version 15.4.1.327 or later
  4. For Reflection Windows Client 7.2 SP1: Apply hotfix 7.2.1186 or later
  5. For Reflection 14.1 SP1: Upgrade to version 14.1.1.206 or later
  6. For Reflection 2008 (all versions), 2008r1 (sp1), 2008r2 (all versions): Contact Attachmate support for specific patch availability
  7. After upgrade, verify the rftpcom.dll version matches the patched release
  8. Test FTP functionality to confirm the upgrade did not break legitimate operations
Caveat Upgrading Reflection software may require reconfiguration of session settings; test thoroughly in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Reflection Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-5012 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-5012 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data