CVE-2024-44229
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 · uneditedAn information leakage was addressed with additional validation. This issue is fixed in Safari 18.1, iOS 18.1 and iPadOS 18.1, macOS Sequoia 15.1, visionOS 2.1. Private browsing may leak some browsing history.
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 · moderate confidenceA privacy vulnerability in Safari's Private Browsing mode could allow browsing history to be leaked. The issue was addressed with additional validation implemented in Safari 18.1, iOS 18.1, iPadOS 18.1, macOS Sequoia 15.1, and visionOS 2.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< 18.1< 18.1< 2.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Check iOS version on iPhoneOpen Settings app, tap General, tap About, and note the version number displayed next to 'Version'Affected if Version is less than 18.1 (for example, 18.0.x or any 17.x release)
-
Check iPadOS version on iPadOpen Settings app, tap General, tap About, and note the version number displayed next to 'Version'Affected if Version is less than 18.1 (for example, 18.0.x or any 17.x release)
-
Check visionOS version on Apple VisionOpen Settings app, tap General, tap About, and note the version number displayed next to 'Version'Affected if Version is less than 2.1 (for example, 2.0.x or any 1.x release)
-
Identify Private Browsing usageDetermine if Safari's Private Browsing mode is used. Look for tabs with the mask icon in Safari or check for recently opened Private tabsAffected if Private Browsing mode has been used on an affected version; the vulnerability allows browsing history to be leaked when this feature is enabled
A user is affected if their device runs iOS/iPadOS below 18.1 or visionOS below 2.1 AND they use Safari's Private Browsing mode, as the leak targets history from Private sessions.
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.
dbcve · scoped2.118.1
Update to Safari 18.1 or later on macOS, or iOS 18.1/iPadOS 18.1 or later on mobile devices. For visionOS, update to version 2.1 or later.
iOS 18.1, iPadOS 18.1, visionOS 2.1
- Back up your device data using iCloud or iTunes/Finder before updating
- Connect your device to Wi-Fi and ensure it has at least 50% battery or is connected to power
- Go to Settings > General > Software Update on your iPhone or iPad
- For Vision Pro, go to Settings > General > Software Update
- Download and install the available update (iOS 18.1, iPadOS 18.1, or visionOS 2.1)
- Restart the device if prompted to complete the installation
- After updating, verify the update in Settings > General > About to confirm the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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-2024-44229 — 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-2024-44229 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