dbcve.org
AndroidOperating system · Google

CVE-2025-22423

HIGH · 7.5 CVSS v3.1 Published 2025-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
In ParseTag of dng_ifd.cpp, there is a possible way to crash the image renderer due to a missing bounds check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

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 confidence

A missing bounds check in the ParseTag function of dng_ifd.cpp (DNG image format parser) allows attackers to trigger an out-of-bounds memory access by providing specially crafted DNG image files, causing the image renderer to crash. No user interaction or elevated privileges are required for exploitation.

MitigationApply vendor security updates to the affected image processing library. Until patched, consider sandboxing image processing workflows or disabling automatic thumbnail generation for untrusted sources.

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
AndroidOperating system
Affected:= 13.0= 14.0= 15.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The reported version is 13.0, 14.0, or 15.0 (exact match)
  2. Identify DNG image processing usage
    Check if the device has apps or services that automatically process DNG image files, such as gallery apps, photo editors, or thumbnail generation services. Inspect installed apps that handle camera RAW files.
    Affected if DNG processing apps or services are present and active on the device
  3. Verify automatic thumbnail generation is enabled
    Check Settings > Photos > Settings (or similar) for options like 'Show thumbnails', 'Generate previews', or 'Process RAW images automatically'. On Android, this may also be found in Google Photos or vendor gallery app settings.
    Affected if Automatic thumbnail or preview generation for DNG files is enabled
  4. Check for DNG library component
    Search for the library containing dng_ifd.cpp on the system. This is typically part of Android's media processing framework. Look in /system/lib/ or /vendor/lib/ for libraries related to DNG/RAW image handling, or check app permissions for camera/storage access that would enable DNG processing.
    Affected if The DNG parsing library is present and the app has permissions to process images

A user is affected if their Android device runs version 13.0, 14.0, or 15.0 and has DNG image processing or automatic thumbnail generation enabled, as the vulnerability triggers when processing specially crafted DNG files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor security updates to the affected image processing library. Until patched, consider sandboxing image processing workflows or disabling automatic thumbnail generation for untrusted sources.

Recommended fix Moderate confidence

Latest Android security update containing the fix for CVE-2025-22423 (Android Security Bulletin)

  1. Check for and install the latest Android system updates on the device by going to Settings > System > Software Update
  2. Ensure the device has the latest Android Security Bulletin patch applied. Go to Settings > About Phone > Android Security Patch Level to verify
  3. If the device manufacturer has released an update containing this fix, apply it. For Pixel devices, ensure you have the latest monthly security update
  4. After updating, verify the fix by confirming the Android Security Patch Level is later than the vulnerability disclosure date
Caveat Standard Android update risks apply - ensure backup of data before applying system updates; some devices may have delayed manufacturer updates

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22423 — 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-22423 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