dbcve.org
SafariWeb browser · Apple

CVE-2014-4465

MEDIUM · 5.0 CVSS v2.0 Published 2014-12-10
Fix available
A fix is available. Upgrade to after 8.1.2 or later.
See remediation →
59/100
Remediation priority · Elevated
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 in Apple Safari before 6.2.1, 7.x before 7.1.1, and 8.x before 8.0.1 allows remote attackers to bypass the Same Origin Policy via crafted Cascading Style Sheets (CSS) token sequences within an SVG file in the SRC attribute of an IMG element.

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 confidence

This is a Same Origin Policy (SOP) bypass vulnerability in WebKit. Attackers exploit crafted CSS token sequences within an SVG file referenced in the SRC attribute of an IMG element to circumvent browser security restrictions, potentially allowing unauthorized access to cross-origin resources.

MitigationUpdate Safari to version 6.2.1, 7.1.1, 8.0.1 or later to obtain the patched WebKit component. Organizations should ensure patch management processes cover desktop browsers.

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.2.0= 7.1.0= 8.0.0
TvosOperating system
Affected:<= 7.0.1
Iphone OsOperating system
Affected:<= 8.1.2

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
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 checks

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

  1. Identify the Safari product and platform
    Determine if Safari is running on macOS, iOS (iPhone/iPad), or tvOS. On macOS, open Safari and go to Safari > About Safari. On iOS, go to Settings > Safari > About. On tvOS, go to Settings > General > About.
    Affected if Safari is installed on any of the affected platforms (macOS, iOS, tvOS)
  2. Check Safari version on macOS
    Open Safari, click Safari menu, select About Safari. Note the version number displayed (e.g., 8.0.0, 7.1.0, 6.2.0).
    Affected if Version is <= 6.2.0, or exactly 7.1.0, or exactly 8.0.0
  3. Check Safari version on iOS
    Open Settings app, scroll to Safari, tap Safari, tap About. Note the Version field (e.g., 8.1.2).
    Affected if Version is <= 8.1.2
  4. Check Safari version on tvOS
    Open Settings app, go to General, select About. Note the Version field (e.g., 7.0.1).
    Affected if Version is <= 7.0.1
  5. Verify WebKit component version if accessible
    In Safari, type 'WebKit' in the address bar or check the Safari configuration files. The WebKit version is typically tied to the Safari version for these Apple products.
    Affected if WebKit bundled with affected Safari versions is in use

A user is affected if they are running Safari on macOS with version <= 6.2.0, 7.1.0, or 8.0.0; on iOS with version <= 8.1.2; or on tvOS with version <= 7.0.1.

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 8.1.2
Interim mitigation

Update Safari to version 6.2.1, 7.1.1, 8.0.1 or later to obtain the patched WebKit component. Organizations should ensure patch management processes cover desktop browsers.

Fix this in Safari Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-4465 — 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-4465 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