dbcve.org
AndroidOperating system · Google

CVE-2022-27823

HIGH · 7.1 CVSS v3.1 Published 2022-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
Improper size check in sapefd_parse_meta_HEADER_old function of libsapeextractor library prior to SMR Apr-2022 Release 1 allows out of bounds read via a crafted media file.

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

The libsapeextractor library contains an improper size check in the sapefd_parse_meta_HEADER_old function that allows an out-of-bounds read when processing a crafted media file. This information disclosure vulnerability could allow an attacker to read sensitive memory contents by providing a malicious media file to the affected software.

MitigationUpdate to SMR Apr-2022 Release 1 or later to obtain the patched libsapeextractor library. Until then, avoid processing untrusted media files with software that uses this library.

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:= 10.0= 11.0= 12.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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. Locate libsapeextractor library on the system
    Search for the libsapeextractor library file using a file manager or command-line tool (e.g., 'find / -name libsapeextractor*' or check common system library directories)
    Affected if The library file is present on the device
  2. Identify the installed version of libsapeextractor
    Check the file properties or metadata of the library to retrieve its version information, or use system diagnostic tools that list installed libraries with version numbers
    Affected if The library version matches Android 10.0, 11.0, or 12.0 systems and is older than the SMR Apr-2022 Release 1 patch
  3. Determine if software using this library is present
    Identify applications or system components that depend on libsapeextractor by checking installed applications or scanning for binaries that link to this library
    Affected if Applications or services that utilize libsapeextractor are installed on the device
  4. Assess media file processing exposure
    Review which applications on the device are configured to process media files (audio/video) and could invoke libsapeextractor functionality during parsing operations
    Affected if Applications that process media files are used and could parse untrusted media content through libsapeextractor
  5. Check system security patch level
    Verify the device's Android security patch level in system settings under 'About Phone' > 'Security Patch Level' to determine if the SMR Apr-2022 Release 1 or later update has been applied
    Affected if The security patch level is earlier than April 2022, indicating the vulnerability remains unpatched

A user is affected if the device runs Android 10.0, 11.0, or 12.0, has the libsapeextractor library present with a version prior to SMR Apr-2022 Release 1, and has applications that process media files using this library.

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

Update to SMR Apr-2022 Release 1 or later to obtain the patched libsapeextractor library. Until then, avoid processing untrusted media files with software that uses this library.

Recommended fix High confidence

SMR Apr-2022 Release 1

  1. Check current Android version on the Samsung device in Settings > About Phone > Software Information
  2. Verify the SMR (Samsung Mobile Security) version in Settings > About Phone > Software Information > SMR (or under Samsung Security section in Settings)
  3. Apply the April 2022 security update by checking for system updates in Settings > Software Update > Download and install
  4. Verify the device is running SMR Apr-2022 Release 1 or later after the update completes

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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