CVE-2010-3972
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 · uneditedHeap-based buffer overflow in the TELNET_STREAM_CONTEXT::OnSendData function in ftpsvc.dll in Microsoft FTP Service 7.0 and 7.5 for Internet Information Services (IIS) 7.0, and IIS 7.5, allows remote attackers to execute arbitrary code or cause a denial of service (daemon crash) via a crafted FTP command, aka "IIS FTP Service Heap Buffer Overrun Vulnerability." NOTE: some of these details are obtained from third party information.
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 confidenceHeap-based buffer overflow in the TELNET_STREAM_CONTEXT::OnSendData function in ftpsvc.dll in Microsoft FTP Service 7.0 and 7.5 for IIS 7.0 and 7.5 allows remote attackers to execute arbitrary code via crafted FTP commands, achieving code execution in the context of the FTP service process.
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= 7.5CVSS 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.
-
Verify IIS version is 7.5Open a command prompt and run: inetmgr, then go to Help > About Internet Information Services, or run: reg query "HKLM\SOFTWARE\Microsoft\Inetmgr\Parameters" /v Version 2>nul or check the IIS version via: appcmd list config /section:system.applicationHost/sitesAffected if The installed IIS version is 7.5 (note: other versions are not affected)
-
Confirm Microsoft FTP Service is installedCheck if FTP Service exists: Open Programs and Features > Turn Windows features on or off > Internet Information Services > FTP Server, or run: sc query ftpsvcAffected if The FTP Service Windows feature is installed (if not present, the vulnerability does not apply)
-
Check if FTP Service is enabled in IISRun: appcmd list config /section:serverRuntime or check IIS Manager > FTP site status under Sites nodeAffected if FTP site or FTP service is configured/enabled in IIS
-
Verify ftpsvc.dll versionLocate the DLL in the IIS directory, typically at %windir%\System32\inetsrv\ftpsvc.dll, right-click > Properties > Details to view File VersionAffected if The file version corresponds to FTP Service 7.5 for IIS 7.5 (compare your version to the affected release)
-
Confirm FTP service process is runningRun: sc query ftpsvc or look for ftpsvc.exe in Task Manager > Services tabAffected if The FTP service (ftpsvc) is running - this is required for exploitation
A user is affected if they are running IIS version 7.5 with the Microsoft FTP Service 7.5 installed, enabled, and actively running, exposing FTP ports to the network.
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 · scopedApply Microsoft security patches for this vulnerability; if patching is not immediately possible, disable the IIS FTP service or restrict network access to FTP ports to limit attack surface.
Apply Microsoft Security Update MS11-004 (security update for IIS FTP Service)
- Apply Microsoft Security Bulletin MS11-004, which addresses this IIS FTP Service heap buffer overflow vulnerability
- Download and install the security update for your Windows version from the Microsoft Update website
- After applying the update, restart the FTP service or reboot the server if required
- Verify the patch is installed by checking for the updated ftpsvc.dll version or via Windows Update history
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3972 — 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-2010-3972 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