CVE-2013-0086
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 · uneditedMicrosoft OneNote 2010 SP1 does not properly determine buffer sizes during memory allocation, which allows remote attackers to obtain sensitive information via a crafted OneNote file, aka "Buffer Size Validation 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 · moderate confidenceThis is an information disclosure vulnerability in Microsoft OneNote 2010 SP1 where the application fails to properly validate buffer sizes during memory allocation. Attackers can exploit this by crafting a malicious OneNote file that triggers improper memory handling, potentially exposing sensitive information from the application's memory space.
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= 2010= 2010CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 installed SharePoint productOpen SharePoint Central Administration, go to System Settings > Manage servers in this farm, or run 'Get-SPProduct -Local' in SharePoint Management Shell to list installed SharePoint products and versionsAffected if Neither Microsoft SharePoint Foundation 2010 nor Microsoft SharePoint Server 2010 is listed as installed
-
Check SharePoint build versionIn SharePoint Central Administration, navigate to Check product and patch installation status under System Settings, or use 'Get-SP farm' in SharePoint Management Shell to retrieve the build numberAffected if The build version cannot be determined or is not clearly documented as patched post-MS13-099
-
Determine if OneNote integration is enabledCheck if the OneNote Web App or OneNote service applications are configured in SharePoint: Run 'Get-SPServiceApplication | Where-Object {$_.DisplayName -like "*OneNote*"}' in SharePoint Management ShellAffected if OneNote service applications exist and are running, as the malicious file would target this integration point
-
Verify memory allocation handlingThis is a binary vulnerability in memory handling - there is no configuration flag. The presence of the vulnerability can only be confirmed by the unpatched product versionAffected if SharePoint 2010 is installed without MS13-099 or subsequent security updates applied
A user is affected if SharePoint Foundation 2010 or SharePoint Server 2010 is installed without the MS13-099 security update applied, particularly when OneNote integration features are enabled.
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 dataApply the relevant Microsoft security update (MS13-099) to patch the buffer size validation vulnerability in OneNote 2010 SP1, or upgrade to a patched version of Microsoft Office.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0086 — 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-2013-0086 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