SafariWeb browser · Apple
CVE-2013-5196
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 · uneditedWebKit, as used in Apple Safari before 6.1.1 and 7.x before 7.0.1, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted web site, a different vulnerability than other WebKit CVEs listed in APPLE-SA-2013-12-16-1.
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 confidenceMemory corruption vulnerability in WebKit rendering engine allows remote code execution or denial of service via crafted malicious web pages. The vulnerability affects Safari browsers before versions 6.1.1 and 7.0.1.
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
SafariWeb browser
<= 6.1= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 7.0<= 12.0<= 7.0.6<= 6.0.2all 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Check installed Safari version on macOS or WindowsOn macOS: open Safari > Safari menu > About Safari. On Windows: open Safari > Help menu > About Safari. Note the full version number displayed.Affected if Version is 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.1, or 7.0 (any version before 6.1.1 or 7.0.1)
-
Check installed iTunes version on WindowsOpen iTunes > Help > About iTunes. Note the version number displayed.Affected if Version is 12.0 or any version <= 12.0
-
Check iOS version on iPhone or iPadGo to Settings > General > About on the iOS device. Note the Version field.Affected if Version is 7.0.6 or any version <= 7.0.6
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV device.Affected if Version is 6.0.2 or any version <= 6.0.2
-
Identify applications using Apple WebKit rendering engineReview installed software for applications that embed the Apple WebKit framework, such as older versions of third-party browsers or custom applications. Check application documentation or binary metadata for WebKit version information.Affected if Any application bundles or ships with an older unpatched WebKit library (all versions of Apple WebKit are affected per the CVE)
You are affected if Safari is before 6.1.1 or 7.0.1, iTunes is 12.0 or earlier, iOS is 7.0.6 or earlier, tvOS is 6.0.2 or earlier, or any application embeds unpatched Apple WebKit.
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 dataUpdate Safari to version 6.1.1 or later (7.0.1+) to obtain patched WebKit. Organizations should deploy standard browser patch management procedures.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5196 — 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-5196 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