dbcve.org
Reflection Ftp ClientApplication · Attachmate

CVE-2014-0603

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
The rftpcom.dll ActiveX control in Attachmate Reflection FTP Client before 14.1.429 allows remote attackers to cause a denial of service (memory corruption) and execute arbitrary code via vectors related to the (1) GetGlobalSettings or (2) GetSiteProperties3 methods, which triggers a dereference of an arbitrary memory address. NOTE: this issue was MERGED with CVE-2014-0606 because it is the same type of vulnerability, affecting the same set of versions, and discovered by the same researcher.

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

The rftpcom.dll ActiveX control in Attachmate Reflection FTP Client versions prior to 14.1.429 contains a memory corruption vulnerability. The GetGlobalSettings and GetSiteProperties3 methods improperly handle memory, leading to dereference of arbitrary memory addresses. This allows remote attackers to cause denial of service through memory corruption and potentially execute arbitrary code.

MitigationUpgrade to Attachmate Reflection FTP Client version 14.1.429 or later. As a compensating control, disable the rftpcom.dll ActiveX control in Internet Explorer or deploy network-level restrictions to prevent exploitation.

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. Check if Attachmate Reflection FTP Client is installed
    Open Control Panel > Programs and Features, or run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" /s' and look for 'Attachmate Reflection' in the display name
    Affected if The application appears in installed programs list
  2. Determine the installed version of Attachmate Reflection FTP Client
    Check the version in Programs and Features, or query the registry key HKLM\SOFTWARE\Attachmate\Reflection\InstallPath or look for version info in the application's executable properties
    Affected if The displayed version number is 14.1.420 or lower, or if no version is shown but the product name matches and no hotfix has been applied
  3. Verify the rftpcom.dll ActiveX component is present
    Search for rftpcom.dll in the installation directory (typically under C:\Program Files\Attachmate\Reflection\) or check registry under HKCR\CLSID\ for the component's CLSID
    Affected if The rftpcom.dll file exists in the Reflection installation folder or is registered as an ActiveX control
  4. Check if the ActiveX control is enabled in Internet Explorer
    Open Internet Explorer > Tools > Manage Add-ons, look for 'Reflection FTP Client' or 'rftpcom' in the list of ActiveX controls
    Affected if The ActiveX control is listed as enabled or 'Allowed' in Internet Explorer add-ons

If Attachmate Reflection FTP Client version 14.1.420 or lower is installed with the rftpcom.dll ActiveX control present and enabled in Internet Explorer, the system is affected by this vulnerability.

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

Upgrade to Attachmate Reflection FTP Client version 14.1.429 or later. As a compensating control, disable the rftpcom.dll ActiveX control in Internet Explorer or deploy network-level restrictions to prevent exploitation.

Recommended fix High confidence

Version 14.1.429 or later

  1. Check the current version of Attachmate Reflection FTP Client by opening the application and navigating to Help > About, or by reviewing installed programs in Control Panel.
  2. Download Reflection FTP Client version 14.1.429 or later from the Attachmate/Micro Focus support portal at support.attachmate.com.
  3. Close all instances of Reflection FTP Client before installing the update.
  4. Run the installer and follow the on-screen prompts to complete the upgrade.
  5. Verify the installation was successful by checking the version number matches 14.1.429 or higher.

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

Fix this in Reflection Ftp Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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