dbcve.org
AndroidOperating system · Google

CVE-2021-25387

CRITICAL · 10.0 CVSS v3.1 Published 2021-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
An improper input validation vulnerability in sflacfd_get_frm() in libsflacextractor library prior to SMR MAY-2021 Release 1 allows attackers to execute arbitrary code on mediaextractor process.

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

Improper input validation vulnerability in the sflacfd_get_frm() function of the libsflacextractor library allows attackers to execute arbitrary code on the mediaextractor process via maliciously crafted media files.

MitigationApply the SMR MAY-2021 Release 1 or later security update to patch the libsflacextractor library; users should accept vendor security patches to address this critical input validation flaw.

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:= 8.1= 9.0= 10.0= 11.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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. Verify Android version
    Check the Android OS version in Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version is 8.1, 9.0, 10.0, or 11.0 (exact matches as listed in affected versions)
  2. Confirm libsflacextractor library presence
    Locate the libsflacextractor library on the device via ADB command: 'find /system/lib* /vendor/lib* -name "*sflacextractor*" 2>/dev/null' or check in /system/lib/ or /vendor/lib/ directories
    Affected if The library file exists on the device, indicating the vulnerable component is present
  3. Check library file version or modification date
    Run 'ls -la' on the found libsflacextractor library file to inspect its last-modified timestamp, or use 'stat' command
    Affected if The library was not updated around May 2021 or later (pre-SMR MAY-2021 Release 1)
  4. Verify Android security patch level
    Check the security patch level via Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The security patch level is earlier than May 2021 (the patch was released in SMR MAY-2021 Release 1)

A user is affected if their Android device runs version 8.1, 9.0, 10.0, or 11.0 AND has a security patch level before May 2021, with the libsflacextractor library present and processing untrusted media 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 the SMR MAY-2021 Release 1 or later security update to patch the libsflacextractor library; users should accept vendor security patches to address this critical input validation flaw.

Recommended fix High confidence

SMR MAY-2021 Release 1 (or later security patch level)

  1. Check the current security patch level on the Samsung device by navigating to Settings > About Phone > Software Information > Security patch level
  2. Ensure the device is connected to a network and check for system updates via Settings > Software Update > Download and install
  3. Apply the SMR MAY-2021 Release 1 security update or later which contains the fix for the libsflacextractor vulnerability
  4. After updating, verify the security patch level reflects May 2021 or later in Settings > About Phone > Software Information
Caveat Standard security update; no expected breaking changes for this patch

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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