CVE-2014-1273
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 · unediteddyld in Apple iOS before 7.1 and Apple TV before 6.1 allows attackers to bypass code-signing requirements by leveraging use of text-relocation instructions in a dynamic library.
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 confidencedyld (Apple's dynamic linker) in iOS before 7.1 and Apple TV before 6.1 contains a vulnerability that allows attackers to bypass code-signing requirements by leveraging text-relocation instructions in a dynamic library. This enables execution of arbitrary unsigned code by exploiting how the dynamic linker handles text relocations.
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<= 6.0.2= 6.0= 6.0.1<= 7.0.6= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5CVSS 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
- None
AV:N/AC:M/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple device typeDetermine whether the device is an iPhone/iPad/iPod touch (iOS) or Apple TV. This matters because they have different version numbering and affected ranges.Affected if Device is an iOS device or Apple TV - the vulnerability affects both platforms but with different version thresholds.
-
Check iOS version on iPhone, iPad, or iPod touchOn the device, go to Settings > General > About > Version. Note the exact version number displayed (for example, 7.0.4 or 6.1.3).Affected if iOS version is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, or 7.0.6 (any version 7.0 through 7.0.6 inclusive). Versions 7.1 and later are not affected.
-
Check Apple TV versionOn the Apple TV, go to Settings > General > About > Version. Note the exact version number displayed (for example, 6.0.1 or 6.0.2).Affected if Apple TV version is 6.0, 6.0.1, or 6.0.2 (any version 6.0 through 6.0.2 inclusive). Version 6.1 and later are not affected.
-
Verify if text relocations could be exploitedThis vulnerability specifically requires that a dynamic library with text-relocation instructions is loaded by the dyld dynamic linker. In normal iOS/Apple TV usage, this is an implementation detail of third-party code. The vulnerability exists in the dyld component itself regardless of specific app configuration.Affected if The device runs an affected iOS version (7.0-7.0.6) or affected Apple TV version (6.0-6.0.2). The vulnerability is present in the dyld component of these versions and can be triggered when loading libraries that contain text-relocation instructions.
You are affected if the device runs iOS version 7.0 through 7.0.6, or Apple TV version 6.0 through 6.0.2. Later versions (iOS 7.1+ and Apple TV 6.1+) include the patch and are not vulnerable.
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 to iOS 7.1 or later and Apple TV 6.1 or later. This vulnerability was patched in these respective versions and does not require custom code changes.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1273 — 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-1273 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