CVE-2014-1267
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 · uneditedThe Configuration Profiles component in Apple iOS before 7.1 and Apple TV before 6.1 does not properly evaluate the expiration date of a mobile configuration profile, which allows attackers to bypass intended access restrictions by using a profile after the date has passed.
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 confidenceThe Configuration Profiles component in Apple iOS before 7.1 and Apple TV before 6.1 fails to properly validate the expiration date of mobile configuration profiles, allowing expired profiles to remain active and continue providing access beyond their intended validity period.
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.
-
Determine the iOS versionGo to Settings > General > About on the iOS device and look at the 'Version' fieldAffected if The version is 7.0.6 or lower, or any 7.0.x version (7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, or 7.0.6)
-
Determine the Apple TV versionGo to Settings > General > About on Apple TV and look at the version numberAffected if The version is 6.0.2 or lower, or exactly 6.0, 6.0.1, or 6.0.2
-
Check for installed mobile configuration profilesOn iOS, go to Settings > General > Profiles and Profile Management. On Apple TV, this may require checking via MDM or config utility. Look for any listed configuration profiles.Affected if Any mobile configuration profiles are installed on the device
-
Inspect profile expiration datesWithin each installed profile, view the profile details and look for 'Expiration' or 'Valid until' dates. Note whether any dates have passed.Affected if Any installed profile shows an expiration date in the past (the bug means these expired profiles may still be active)
You are affected if your device runs iOS 7.0.6 or below or Apple TV 6.0.2 or below AND has mobile configuration profiles installed, particularly if any profiles have expired dates that are still being honored by the system.
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 dataUpgrade to iOS 7.1 or later and Apple TV 6.1 or later to receive the patch that enforces proper profile expiration validation.
- 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-2014-1267 — 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-1267 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