CVE-2024-54492
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 · uneditedThis issue was addressed by using HTTPS when sending information over the network. This issue is fixed in iOS 18.2 and iPadOS 18.2, iPadOS 17.7.3, macOS Sequoia 15.2, visionOS 2.2. An attacker in a privileged network position may be able to alter network traffic.
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 confidenceThis vulnerability allowed network traffic to be sent in cleartext (HTTP) instead of encrypted (HTTPS), enabling an attacker with privileged network position to intercept and modify communications between the affected Apple devices and remote servers.
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< 17.7.3>= 18.0, < 18.2< 18.2< 15.2< 2.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 iPhone or iPad OS versionOn the device, go to Settings > General > About and look at the 'Version' fieldAffected if The version shows iOS or iPadOS lower than 17.7.3, or between 18.0 and 18.2 (not including 18.2)
-
Check macOS versionGo to System Settings > About, or run 'sw_vers' in Terminal, and note the version numberAffected if The macOS version is lower than 15.2 (for example, 15.1, 14.x, 13.x, etc.)
-
Check visionOS versionOn Apple Vision, go to Settings > General > About and find the version numberAffected if The visionOS version is lower than 2.2
A device is affected if it runs any version below the security-patched releases: iOS/iPadOS 17.7.3 or 18.2, macOS 15.2, or visionOS 2.2
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.215.217.7.3
Update affected devices to the patched versions: iOS 18.2, iPadOS 18.2 or 17.7.3, macOS Sequoia 15.2, or visionOS 2.2.
iOS 18.2 / iPadOS 18.2 / iPadOS 17.7.3 / macOS Sequoia 15.2 / visionOS 2.2
- Identify the Apple device type (iPhone, iPad, Mac, or Vision Pro)
- Check the current OS version in Settings > General > About on iOS/iPadOS, System Settings > General on macOS, or Settings > About on visionOS
- For iPhone: upgrade to iOS 18.2 or later
- For iPad: upgrade to iPadOS 18.2 or iPadOS 17.7.3
- For Mac: upgrade to macOS Sequoia 15.2 or later
- For Vision Pro: upgrade to visionOS 2.2 or later
- Ensure the device is connected to power during the update process
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-54492 — 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-54492 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