Reflection Ftp ClientApplication · Attachmate

CVE-2014-0605

HIGH · 10.0 CVSS v2.0 Published 2015-02-06
Fix available
A fix is available. Upgrade to after 14.1.420 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Directory 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 SaveSettings 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 confidence

A directory traversal vulnerability exists in the rftpcom.dll ActiveX control component of Attachmate Reflection FTP Client versions prior to 14.1.429. The vulnerability resides in the SaveSettings method, which fails to properly sanitize path traversal sequences, allowing attackers to write arbitrary files to the filesystem and achieve remote code execution.

MitigationUpdate Attachmate Reflection FTP Client to version 14.1.429 or later to patch the vulnerable ActiveX control. If immediate patching is not feasible, disable the ActiveX control in Internet Explorer and restrict browser access to untrusted sites.

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
Reflection Ftp ClientApplication
Affected:<= 14.1.420

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. Verify Attachmate Reflection FTP Client is installed
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Attachmate Reflection FTP Client, or check Program Files for the Attachmate installation folder.
    Affected if The product is found in the registry or filesystem.
  2. Determine the installed version number
    Locate the registry entry or the main executable (typically ReflectionFTP.exe) and retrieve its FileVersion property through right-click Properties in Windows Explorer.
    Affected if The reported version is 14.1.420 or lower.
  3. Confirm the vulnerable ActiveX component exists
    Search for the file rftpcom.dll on the system, typically located in the Reflection installation directory under a bin or system folder.
    Affected if rftpcom.dll is present on the system.
  4. Verify the ActiveX control is registered
    Check the Windows registry under HKCR\CLSID for the CLSID associated with rftpcom.dll, or examine IE add-ons for the Reflection FTP Client ActiveX control.
    Affected if The ActiveX control is registered and enabled in Internet Explorer or as a COM component.

A user is affected if Attachmate Reflection FTP Client version 14.1.420 or lower is installed and the rftpcom.dll ActiveX control is present and registered on the system.

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
Upgrade available Upgrade to a release after 14.1.420
Interim mitigation

Update Attachmate Reflection FTP Client to version 14.1.429 or later to patch the vulnerable ActiveX control. If immediate patching is not feasible, disable the ActiveX control in Internet Explorer and restrict browser access to untrusted sites.

Recommended fix High confidence

14.1.429

  1. Obtain Attachmate Reflection FTP Client version 14.1.429 or later from the official Attachmate/Micro Focus vendor website
  2. Uninstall the current version of Reflection FTP Client (version 14.1.420 or earlier)
  3. Install the updated version (14.1.429 or later)
  4. Restart the application and verify the rftpcom.dll ActiveX control is updated

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

Fix this in Reflection Ftp Client Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0605 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0605 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