CVE-2013-0095
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 · uneditedOutlook in Microsoft Office for Mac 2008 before 12.3.6 and Office for Mac 2011 before 14.3.2 allows remote attackers to trigger access to a remote URL and consequently confirm the rendering of an HTML e-mail message by including unspecified HTML5 elements and leveraging the installation of a WebKit browser on the victim's machine, aka "Unintended Content Loading 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 confidenceThis vulnerability allows remote attackers to confirm whether Outlook for Mac renders HTML emails by embedding specific HTML5 elements that trigger the victim's machine to make requests to attacker-controlled URLs, exploiting the WebKit browser integration.
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= 2008= 2011CVSS 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 Microsoft Office for Mac versionOpen any Office application (Word, Excel, or Outlook), go to the application menu, select 'About Microsoft [App]' and note the version number displayed. Alternatively, run: defaults read /Applications/Microsoft\ Outlook.app/Contents/Info.plist CFBundleVersionAffected if The version displayed is 2008 (any build) or 2011 (any build)
-
Check if Outlook for Mac is configured to automatically load remote content in HTML emailsIn Outlook, go to Preferences > Security (or Privacy in newer versions) and examine the 'Download remote content in HTML messages' settingAffected if Remote content loading is enabled (this is the default setting) and the Outlook version is 2008 or 2011
-
Verify the specific Office build numberIf About dialog shows '12.3.6' or lower for Office 2008, or '14.3.2' or lower for Office 2011, these are vulnerable builds. Run: defaults read /Applications/Microsoft\ Outlook.app/Contents/Info.plist CFBundleShortVersionStringAffected if The build number is 12.3.6 or lower (Office 2008), or 14.3.2 or lower (Office 2011)
The environment is affected if Microsoft Office for Mac 2008 or 2011 is installed with remote content loading enabled and the build version is at or below 12.3.6 (Office 2008) or 14.3.2 (Office 2011).
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 Microsoft Office for Mac security updates 12.3.6 (for Office 2008) or 14.3.2 (for Office 2011) or later, which prevent automatic loading of remote content.
- 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-2013-0095 — 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-0095 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