dbcve.org
AndroidOperating system · Samsung

CVE-2025-58477

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
Out-of-bounds write in parsing IFD tag in libimagecodec.quram.so prior to SMR Dec-2025 Release 1 allows remote attackers to access out-of-bounds 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 · moderate confidence

An out-of-bounds write vulnerability exists in libimagecodec.quram.so when parsing IFD (Image File Directory) tags in image files. This occurs prior to the SMR Dec-2025 Release 1 update. The vulnerability allows remote attackers to write to memory locations outside the intended buffer boundaries, potentially leading to memory corruption or information disclosure. The attack likely involves crafting malicious image files (e.g., TIFF) that trigger the improper bounds checking during IFD tag parsing.

MitigationApply the SMR Dec-2025 Release 1 or later Samsung firmware update which patches libimagecodec.quram.so. Until the vendor patch is available, avoid opening untrusted image files from unknown sources, as the attack vector is remote via image processing.

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= 16.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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. Check Samsung Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 13.0, 14.0, 15.0, or 16.0 (unpatched) - note that the '=' in the advisory likely indicates specific affected versions rather than a range
  2. Locate libimagecodec.quram.so library
    Search for the file via ADB: 'find / -name libimagecodec.quram.so 2>/dev/null' or check /vendor/lib64/ or /system/lib64/ directories
    Affected if The library exists on the device - this confirms Samsung's image codec is present
  3. Check if SMR Dec-2025 update is applied
    Run 'getprop ro.build.version.sem' or check Samsung Software Maintenance Release version in Settings > About Phone > Software info, or run 'getprop ro.build.version.oneui'
    Affected if The SMR version is earlier than December 2025 Release 1, meaning the patch is not yet applied
  4. Verify IFD tag parsing is used
    Identify apps that process TIFF images or other formats using IFD tags - check which apps have media/image processing permissions and use image decoding
    Affected if Any app that processes untrusted image files using the vulnerable library is potentially exploitable; the attack vector is parsing malicious image files (e.g., TIFF) with crafted IFD tags

A device is affected if it runs Samsung Android 13.0, 14.0, 15.0, or 16.0 with an unpatched libimagecodec.quram.so (SMR Dec-2025 Release 1 not applied) and processes image files through the vulnerable codec.

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 the SMR Dec-2025 Release 1 or later Samsung firmware update which patches libimagecodec.quram.so. Until the vendor patch is available, avoid opening untrusted image files from unknown sources, as the attack vector is remote via image processing.

Recommended fix High confidence

SMR Dec-2025 Release 1 (December 2025 Samsung Security Maintenance Release)

  1. Check the current Android security patch level on the Samsung device in Settings > About Phone > Software Information > Security patch level
  2. Verify if the device has received the SMR Dec-2025 Release 1 security update
  3. If not updated, check for available software updates: Settings > Software Update > Download and install
  4. Apply the December 2025 Samsung Security Maintenance Release (SMR) which contains the fix for the out-of-bounds write vulnerability in libimagecodec.quram.so
  5. After updating, verify the security patch level shows December 2025 or later
Caveat Security updates are cumulative; applying this patch should not introduce functional breaking changes but requires normal update process

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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