CVE-2014-5211
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 · uneditedStack-based buffer overflow in the Attachmate Reflection FTP Client before 14.1.433 allows remote FTP servers to execute arbitrary code via a large PWD response.
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 confidenceStack-based buffer overflow in Attachmate Reflection FTP Client versions before 14.1.433 allows remote malicious FTP servers to execute arbitrary code by sending an oversized PWD (Print Working Directory) response that overwrites stack memory.
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= 14.1.429CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Locate Attachmate Reflection FTP Client installationCheck Program Files folder for 'Attachmate' or 'Reflection' directories, or search for 'reflection.exe' in the installation paths. On Windows, also check the registry under HKLM\SOFTWARE\Attachmate or HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entry names containing 'Reflection FTP'.Affected if The product is not found on the system, then it is not affected.
-
Determine installed version numberRight-click the Reflection FTP Client executable (typically 'reflection.exe' or 'rfm.exe'), select Properties, and check the Details tab for the File Version. Alternatively, launch the application and navigate to Help > About Reflection to view the exact version.Affected if Version is 14.1.429 or any version lower than 14.1.433.
-
Verify FTP client usage contextCheck if the Reflection FTP Client is configured with saved FTP server connections, or review recent FTP connection logs. The vulnerability is triggered only when the client connects to a malicious FTP server that sends an oversized PWD response.Affected if The client has been used to connect to untrusted or external FTP servers.
User is affected if Attachmate Reflection FTP Client version 14.1.429 or any version before 14.1.433 is installed and has been used to connect to FTP servers.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Attachmate Reflection FTP Client to version 14.1.433 or later to patch the stack-based buffer overflow vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-5211 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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