CVE-2014-0604
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 · uneditedDirectory traversal vulnerability in the rftpcom.dll ActiveX control in Attachmate Reflection FTP Client before 14.1.429 allows remote attackers to execute arbitrary code via unspecified vectors to the StartLog method.
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 confidenceA directory traversal vulnerability exists in the rftpcom.dll ActiveX control within Attachmate Reflection FTP Client versions prior to 14.1.429. The flaw resides in the StartLog method, which fails to properly validate path traversal sequences, allowing remote attackers to manipulate file paths and execute arbitrary code on the affected system.
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.420CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Attachmate Reflection FTP Client is installedCheck the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Attachmate Reflection FTP Client' or inspect Program Files for a folder containing 'Attachmate' and 'Reflection' in the name.Affected if No entry or folder is found - the product is not installed and not affected.
-
Determine the installed version numberLocate the product in the Windows registry uninstall key and read the 'DisplayVersion' value, or right-click the application executable in its installation folder and view Properties > Details to find the File Version.Affected if The version is 14.1.420 or lower - the installed version falls within the affected range.
-
Verify the vulnerable rftpcom.dll ActiveX control existsSearch for the file rftpcom.dll on the system, typically found in the application's installation directory (e.g., C:\Program Files\Attachmate\Reflection\), or check if it is registered as an ActiveX control in the registry under HKLM\SOFTWARE\Classes\CLSID\.Affected if The rftpcom.dll file exists and is registered as an ActiveX component - the vulnerable component is present.
-
Check if the ActiveX control is enabled in Internet ExplorerOpen Internet Explorer, navigate to Tools > Manage Add-ons, and look for 'Reflection FTP Client' or 'rftpcom.dll' in the list of ActiveX controls to see if it is enabled.Affected if The ActiveX control appears in the enabled state - it can be invoked by malicious web content.
A user is affected if Attachmate Reflection FTP Client version 14.1.420 or lower is installed with the rftpcom.dll ActiveX control present and enabled.
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.
dbcve · scopedUpgrade Attachmate Reflection FTP Client to version 14.1.429 or later to obtain the patched ActiveX control. Alternatively, disable the rftpcom.dll ActiveX control in Internet Explorer or restrict its deployment via group policy until the upgrade can be applied.
Reflection FTP Client 14.1.429 or later
- 1. Identify all systems with Attachmate Reflection FTP Client installed by scanning systems for the rftpcom.dll ActiveX control or the Reflection FTP Client application
- 2. Check the currently installed version of Reflection FTP Client (typically found in Add/Remove Programs or by checking file properties of the executable)
- 3. Uninstall the vulnerable version (14.1.420 or earlier) from all affected systems
- 4. Download and install Reflection FTP Client version 14.1.429 or later from the official Attachmate/Micro Focus support site
- 5. Verify the new version is correctly installed by checking the version number in Add/Remove Programs
- 6. Test the upgraded Reflection FTP Client to ensure normal FTP functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- 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-0604 — 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-0604 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