dbcve.org
AndroidOperating system · Google

CVE-2022-27824

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 of in sapefd_parse_meta_DESCRIPTION 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 · moderate confidence

An improper size check in the sapefd_parse_meta_DESCRIPTION function of the libsapeextractor library allows an out-of-bounds read when parsing a crafted media file. The vulnerability stems from insufficient validation of size parameters before reading memory, potentially allowing an attacker to access sensitive information from adjacent memory locations.

MitigationUpdate to SMR Apr-2022 Release 1 or later which contains the proper size validation fix. Until then, exercise caution when processing untrusted media files with applications using libsapeextractor.

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. Identify libsapeextractor library presence
    Search for the file libsapeextractor.so on the Android device, typically found in /system/lib64/ or /system/lib/ directories. Use 'find /system -name libsapeextractor.so 2>/dev/null' or check via file explorer if you have root access.
    Affected if The library file exists on the device, indicating the vulnerable component is present.
  2. Determine Android OS version
    Go to Settings > About Phone > Android version (or Settings > System > About Phone > Android version on newer devices). Record the exact version number displayed.
    Affected if The Android version is exactly 10.0, 11.0, or 12.0, matching the affected version range.
  3. Check Android security patch level
    Navigate to Settings > About Phone > Security patch level (or Settings > System > About Phone > Security patch level). Record the date shown (e.g., April 1, 2022 or later).
    Affected if The security patch level is earlier than April 2022, meaning the fix (SMR Apr-2022 Release 1) has not been applied.
  4. Identify applications using libsapeextractor
    Review installed applications that process media files (video players, audio tools, media converters). The library is used by applications that handle Samsung-specific media formats. Check application permissions for media file access.
    Affected if Applications that parse media files are installed and have permission to access media content, providing an attack vector.

A user is affected if their Android device runs version 10.0, 11.0, or 12.0, contains the libsapeextractor library, and has a security patch level earlier than April 2022.

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 which contains the proper size validation fix. Until then, exercise caution when processing untrusted media files with applications using libsapeextractor.

Recommended fix Moderate confidence

SMR Apr-2022 Release 1

  1. Open Settings on your Samsung Android device
  2. Navigate to Settings > Software update
  3. Tap on Download and install to check for available updates
  4. Ensure the device updates to the April 2022 Samsung Security Patch level (SMR Apr-2022 Release 1)
  5. Verify the update was applied by checking Settings > About phone > Software information and confirming the Security patch level shows April 2022

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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