dbcve.org
AndroidOperating system · Samsung

CVE-2025-20993

MEDIUM · 6.8 CVSS v3.1 Published 2025-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
Out-of-bounds write in libsecimaging.camera.samsung.so prior to SMR Jun-2025 Release 1 allows local attackers to write 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 libsecimaging.camera.samsung.so prior to the SMR Jun-2025 Release 1. This memory corruption flaw allows local attackers to write to memory locations outside the intended bounds, potentially leading to arbitrary code execution or denial of service.

MitigationApply the Samsung SMR Jun-2025 security update or later to affected devices to obtain the patched version of libsecimaging.camera.samsung.so. Until the patch is applied, limit local access to vulnerable devices and monitor for exploitation attempts.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Identify Samsung Android version
    Go to Settings > About Phone > Android version and verify the device is running Android 13.0, 14.0, or 15.0
    Affected if Device runs Android 13.0, 14.0, or 15.0 on a Samsung device
  2. Locate the vulnerable library
    On the device, navigate to the library directory (typically /vendor/lib64 or /system/lib64) and locate the file named libsecimaging.camera.samsung.so
    Affected if The file libsecimaging.camera.samsung.so exists on the device
  3. Determine the library version
    Check the file properties or metadata of libsecimaging.camera.samsung.so to obtain its version or build date. This may require using a file manager with metadata viewing capabilities or running 'ls -la' via ADB shell
    Affected if The library version or build date is earlier than the SMR Jun-2025 Release 1 patch date
  4. Verify if security patch is applied
    Go to Settings > About Phone > Security patch level and check if the June 2025 security update has been applied
    Affected if The security patch level is earlier than June 2025 or the field is empty/unknown

The device is affected if it is a Samsung Android device running version 13.0, 14.0, or 15.0 and the libsecimaging.camera.samsung.so library version predates the SMR Jun-2025 Release 1 update.

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 Samsung SMR Jun-2025 security update or later to affected devices to obtain the patched version of libsecimaging.camera.samsung.so. Until the patch is applied, limit local access to vulnerable devices and monitor for exploitation attempts.

Recommended fix High confidence

SMR Jun-2025 Release 1 (June 2025 Samsung Security Maintenance Release)

  1. Check current Android version and security patch level on the Samsung device under Settings > About phone > Software information
  2. Navigate to Settings > Security and privacy > Security update or Settings > About phone > Software update
  3. Check for and install the June 2025 Samsung Security Maintenance Release (SMR Jun-2025 Release 1) or later
  4. Verify the device has been updated by checking Settings > About phone > Software information > Security patch level shows June 2025 or later
Caveat Samsung security updates are generally cumulative; installing the June 2025 SMR should not introduce breaking changes but will include all prior 2025 patches

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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