dbcve.org
SafariWeb browser · Apple

CVE-2014-1338

MEDIUM · 6.8 CVSS v2.0 Published 2014-05-22
Fix available
A fix is available. Upgrade to after 6.1.3 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
WebKit, as used in Apple Safari before 6.1.4 and 7.x before 7.0.4, 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-2014-05-21-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 confidence

Memory corruption vulnerability in WebKit rendering engine allows remote code execution or denial of service via malicious webpage. Attackers can exploit this client-side vulnerability by tricking users into visiting crafted websites that trigger memory corruption in Safari's WebKit component.

MitigationDeploy Safari updates to versions 6.1.4 or 7.0.4 or later across all affected endpoints. This is a client-side patch deployment requiring inventory assessment, update rollout, and verification.

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
Affected:<= 6.1.3= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 6.1= 6.1.1= 6.1.2= 7.0= 7.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Safari version
    On macOS, open Safari and go to Safari > About Safari, or check /Applications/Safari.app/Contents/Info.plist for CFBundleShortVersionString
    Affected if The displayed version matches any of these: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.1, 6.1.1, 6.1.2, 6.1.3, 7.0, 7.0.1 or any version lower than 6.1.4
  2. Check for Safari updates via system
    On macOS, open the App Store and check Updates tab, or run Software Update via system preferences
    Affected if An update to Safari 6.1.4 or 7.0.4 or later is available but has not been installed
  3. Confirm WebKit usage context
    Determine if Safari or any application using WebKit (such as third-party browsers) is actively used on the endpoint
    Affected if Safari or WebKit-based browsers are in regular use and the version falls within the affected range

An endpoint is affected if Safari version 6.0 through 7.0.1 or any version up to 6.1.3 is installed and WebKit-based browsing is occurring on that system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 6.1.3
Interim mitigation

Deploy Safari updates to versions 6.1.4 or 7.0.4 or later across all affected endpoints. This is a client-side patch deployment requiring inventory assessment, update rollout, and verification.

Fix this in Safari Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,850
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1338 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1338 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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