CVE-2002-0977
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 · uneditedBuffer overflow in Microsoft File Transfer Manager (FTM) ActiveX control before 4.0 allows remote attackers to execute arbitrary code via a long TS value.
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 confidenceBuffer overflow vulnerability in Microsoft File Transfer Manager (FTM) ActiveX control in versions prior to 4.0 allows remote attackers to execute arbitrary code by sending an overly long TS value to the vulnerable control.
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 dataall versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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 File Transfer Manager installationSearch for ftm32.exe or ftm.exe in common program directories (C:\Program Files\Microsoft Files\File Transfer Manager, C:\Program Files\File Transfer Manager) or use 'dir /s C:\ftm*.exe' from an elevated command promptAffected if The executable is found on the system, indicating FTM is installed
-
Check installed FTM versionRight-click the ftm32.exe or ftm.exe file, select Properties, then go to the Details tab to view the File VersionAffected if The version number is found to be below 4.0 (for example, 1.x, 2.x, 3.x) or if version cannot be determined but the file exists
-
Verify ActiveX control registrationOpen Registry Editor and search for CLSID entries related to File Transfer Manager (look under HKEY_CLASSES_ROOT for 'FileTransferManager' or 'FTM' related keys), or run 'reg query HKLM\SOFTWARE\Classes /s | findstr -i "File Transfer Manager"' from command promptAffected if The ActiveX control CLSID is registered in the Windows registry
-
Check for vulnerable control in web browser contextIf the ActiveX control is present, it could be instantiated by malicious web pages; inspect browser add-ons or use 'reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ModuleUsage' to find ActiveX dependenciesAffected if The FTM ActiveX control is registered and accessible to Internet Explorer or other browsers
The environment is affected if Microsoft File Transfer Manager is installed with a version prior to 4.0 and the ActiveX control is registered on the system.
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 Microsoft File Transfer Manager to version 4.0 or later to remediate this vulnerability, or disable the ActiveX control if upgrade is not feasible.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0977 — 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-2002-0977 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