SafariWeb browser · Apple
CVE-2015-7099
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 in Apple iOS before 9.2, Safari before 9.0.2, and tvOS before 9.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-2015-7048, CVE-2015-7095, CVE-2015-7096, CVE-2015-7097, CVE-2015-7098, CVE-2015-7100, CVE-2015-7101, CVE-2015-7102, and CVE-2015-7103.
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 confidenceWebKit contains a memory corruption vulnerability that allows remote attackers to execute arbitrary code or cause a denial of service via a crafted website. The vulnerability affects iOS devices before version 9.2, Safari browsers before 9.0.2, and tvOS devices before version 9.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
SafariWeb browser
<= 9.0.1<= 9.0<= 9.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 Apple device typeDetermine whether the device is a Mac running Safari, an iPhone/iPad running iOS, or an Apple TV running tvOS. This dictates which version check to perform next.Affected if Device is a Mac, iPhone, iPad, or Apple TV using Safari, iOS, or tvOS respectively.
-
Check Safari version on macOSOpen Safari, click Safari in the menu bar, select About Safari. The version number appears next to the Safari logo. Compare it to the affected range: versions 9.0.1 and earlier are vulnerable.Affected if Safari version is 9.0.1 or earlier on macOS.
-
Check iOS version on iPhone or iPadOpen Settings app, tap General, tap About. The version number is shown next to Version. Compare it to the affected range: iOS versions 9.1 and earlier are vulnerable.Affected if iOS version is 9.1 or earlier on iPhone or iPad.
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About. The tvOS version is displayed. Compare it to the affected range: tvOS versions 9.0 and earlier are vulnerable.Affected if tvOS version is 9.0 or earlier on Apple TV.
-
Verify WebKit-based browsing is enabledConfirm that Safari or any WebKit-based browser is installed and functional on the device. The vulnerability is triggered by visiting a crafted website, so browsing capability must be present.Affected if Safari or a WebKit-based browser is installed and can access websites.
A user is affected if they are running Safari 9.0.1 or earlier on macOS, iOS 9.1 or earlier on iPhone/iPad, or tvOS 9.0 or earlier on Apple TV, and have web browsing functionality enabled.
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 dataApply vendor patches by updating iOS to 9.2 or later, Safari to 9.0.2 or later, and tvOS to 9.1 or later across all affected devices.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7099 — 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-7099 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