CVE-2010-3964
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 · uneditedUnrestricted file upload vulnerability in the Document Conversions Launcher Service in Microsoft Office SharePoint Server 2007 SP2, when the Document Conversions Load Balancer Service is enabled, allows remote attackers to execute arbitrary code via a crafted SOAP request to TCP port 8082, aka "Malformed Request Code Execution Vulnerability."
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 confidenceUnrestricted file upload vulnerability in the Document Conversions Launcher Service of Microsoft Office SharePoint Server 2007 SP2 allows remote attackers to execute arbitrary code via crafted SOAP requests to TCP port 8082 when the Document Conversions Load Balancer Service is enabled.
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= 2007CVSS 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.
-
Identify SharePoint Server versionCheck the installed version of Microsoft SharePoint Server by reviewing installed programs in Control Panel or using the SharePoint Administration Central website (typically at /_admin/FarmManagement.aspx). Look for Microsoft Office SharePoint Server 2007.Affected if The installed version is Microsoft Office SharePoint Server 2007 (any patch level).
-
Verify Document Conversions Load Balancer Service statusOpen Windows Services console (services.msc) and locate the 'Document Conversions Load Balancer Service'. Check if its Startup type is set to Automatic or Manual and if the service status shows Running.Affected if The Document Conversions Load Balancer Service is enabled (set to Automatic or Manual startup and currently running).
-
Check if TCP port 8082 is listeningOpen Command Prompt and run 'netstat -an | findstr :8082' or use PowerShell with 'Get-NetTCPConnection -LocalPort 8082' to see if port 8082 is in a listening state.Affected if TCP port 8082 is open and listening on any network interface accessible to potential attackers.
-
Confirm Document Conversions Launcher Service is configuredReview SharePoint Central Administration under 'Office SharePoint Server Shared Services' or 'Converted Documents' settings. Verify that Document Conversions Launcher service is configured and pointing to TCP port 8082.Affected if The Document Conversions Launcher Service is configured and bound to port 8082, making the vulnerable endpoint accessible.
A system is affected if it runs SharePoint Server 2007 with the Document Conversions Load Balancer Service enabled and TCP port 8082 accessible, which exposes the vulnerable Document Conversions Launcher Service to crafted SOAP requests.
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 dataDisable the Document Conversions Load Balancer Service if not required for business operations, or block inbound TCP port 8082 at the network perimeter firewall to prevent external exploitation.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3964 — 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-3964 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