CVE-2015-1105
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 TCP implementation in the kernel in Apple iOS before 8.3, Apple OS X before 10.10.3, and Apple TV before 7.2 does not properly implement the Urgent (aka out-of-band data) mechanism, which allows remote attackers to cause a denial of service via crafted packets.
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 TCP implementation in Apple kernel versions prior to iOS 8.3, OS X 10.10.3, and Apple TV 7.2 contains a flaw in processing the Urgent pointer mechanism (RFC 793), which handles out-of-band data. Remote attackers can send crafted packets with malformed urgent data to trigger a denial of service condition in the kernel's network stack.
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<= 10.10.2<= 8.2<= 7.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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Determine if the device runs iOS and its versionOn the device, go to Settings > General > About and look at the 'Version' field, or run 'sw_vers' via terminal on a Mac if iTunes is available. For iOS devices, this typically requires physical access or MDM enrollment data.Affected if The iOS version is 8.2 or earlier (e.g., 8.0, 7.x, 6.x)
-
Determine if the device runs OS X and its versionOn a Mac, click the Apple menu > About This Mac, or run the command 'sw_vers -productVersion' in Terminal.Affected if The OS X version is 10.10.2 or earlier (e.g., 10.10.0, 10.10.1, 10.9.x)
-
Determine if the device runs Apple TV OS and its versionOn Apple TV, go to Settings > General > About > Version, or check the device management/MDM inventory if centrally managed.Affected if The Apple TV OS version is 7.1 or earlier (e.g., 7.0, 6.x)
-
Confirm the vulnerable TCP Urgent pointer feature is in useThis is a kernel-level TCP implementation flaw. The vulnerability triggers when the kernel processes malformed urgent data in incoming TCP packets. No specific user-facing feature must be enabled; any active network listener (Wi-Fi, cellular) can receive the malicious packets.Affected if The device has any network connectivity and is running a vulnerable OS version
A device is affected if it runs iOS 8.2 or earlier, OS X 10.10.2 or earlier, or Apple TV OS 7.1 or earlier, regardless of specific configuration, since the flaw is in the kernel TCP stack processing urgent pointer fields in incoming packets.
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 8.3 or later, OS X 10.10.3 or later, or Apple TV 7.2 or later to obtain the patched kernel TCP implementation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1105 — 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-2015-1105 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