dbcve.org
IpadosOperating system · Apple

CVE-2025-24182

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 15.4 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
An out-of-bounds read issue was addressed with improved input validation. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4. Processing a maliciously crafted font may result in the disclosure of process memory.

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 confidence

An out-of-bounds read vulnerability in the font parsing subsystem allows a maliciously crafted font file to trigger memory disclosure. The vulnerability stems from insufficient input validation during font processing, allowing an attacker to read beyond allocated buffer boundaries and expose process memory contents.

MitigationApply the vendor-supplied patches (iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4) to affected devices. Avoid processing untrusted font files from unknown sources until patches are applied.

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
IpadosOperating system
Affected:< 18.4
Iphone OsOperating system
Affected:< 18.4
macOSOperating system
Affected:>= 15.0, < 15.4
VisionosOperating system
Affected:< 2.4

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the operating system and version
    On iOS/iPadOS: Settings > General > About > Version. On macOS: Apple menu > About This Mac > Version. On visionOS: Settings > General > About > Version.
    Affected if The detected version falls within any of the vulnerable ranges below.
  2. Compare iOS version against affected range
    Check if iOS version is less than 18.4. Go to Settings > General > About on the device.
    Affected if iOS version is < 18.4
  3. Compare iPadOS version against affected range
    Check if iPadOS version is less than 18.4. Go to Settings > General > About on the device.
    Affected if iPadOS version is < 18.4
  4. Compare macOS version against affected range
    Check if macOS version is 15.0 through 15.3.x. Go to Apple menu > About This Mac.
    Affected if macOS version is >= 15.0 AND < 15.4 (includes 15.0, 15.1, 15.2, 15.3)
  5. Compare visionOS version against affected range
    Check if visionOS version is less than 2.4. Go to Settings > General > About.
    Affected if visionOS version is < 2.4

You are affected if your device runs iOS < 18.4, iPadOS < 18.4, macOS 15.0-15.3.x, or visionOS < 2.4, and you process font files from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.4 / 15.4 / 18.4 or later
Fixed in 2.415.418.4
Interim mitigation

Apply the vendor-supplied patches (iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4) to affected devices. Avoid processing untrusted font files from unknown sources until patches are applied.

Recommended fix High confidence

iOS 18.4 / iPadOS 18.4 / macOS Sequoia 15.4 / visionOS 2.4

  1. Identify the Apple device type (iPhone, iPad, Mac, or Vision Pro)
  2. Determine the current OS version from Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
  3. For iPhone/iPad: Upgrade to iOS 18.4 or iPadOS 18.4 via Settings > General > Software Update
  4. For Mac: Upgrade to macOS Sequoia 15.4 via System Settings > General > Software Update
  5. For Vision Pro: Upgrade to visionOS 2.4 via Settings > General > Software Update
  6. After upgrade, verify the fix by confirming the new OS version in Settings
Caveat Standard Apple OS upgrade considerations apply - review app compatibility and back up data before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24182 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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