CVE-2014-1292
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 iOS before 7.1 and Apple TV before 6.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 CVE-2014-1289, CVE-2014-1290, CVE-2014-1291, CVE-2014-1293, and CVE-2014-1294.
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 confidenceMemory corruption vulnerability in WebKit (CVE-2014-1292) allows remote code execution or denial of service via malicious website. Exploits crafted web pages that trigger memory corruption when rendered in Safari on iOS before 7.1 or Apple TV before 6.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<= 7.0.6= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5<= 6.0.2= 6.0= 6.0.1CVSS 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.
-
Identify the device typeDetermine if the target device is an iOS device (iPhone, iPad, iPod touch) or an Apple TV. This matters because they have different version ranges.Affected if Device is an iOS device running a version below 7.1, or an Apple TV running a version below 6.1
-
Check iOS version on iPhone, iPad, or iPod touchOn the iOS device, go to Settings > General > About > Version. Note the displayed version number.Affected if Version starts with 7.0 (such as 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, or 7.0.6)
-
Check Apple TV software versionOn Apple TV, go to Settings > General > About > Version. Note the displayed version number.Affected if Version starts with 6.0 (such as 6.0, 6.0.1, or 6.0.2)
-
Confirm Safari browser is in useVerify that Safari is the default web browser on the device (it is the default out-of-the-box browser on iOS). The vulnerability is triggered when Safari renders a malicious web page.Affected if Safari is used as the default browser on an affected iOS or Apple TV version
The device is affected if it is an iOS device running version 7.0.x or below, or an Apple TV running version 6.0.x or below, and Safari is used to browse the web.
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 affected devices (iOS devices to 7.1+, Apple TV to 6.1+) to patch the WebKit vulnerability and prevent remote code execution from malicious websites.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1292 — 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-2014-1292 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