dbcve.org
AndroidOperating system · Google

CVE-2022-27570

CRITICAL · 9.8 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 →
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
Heap-based buffer overflow vulnerability in parser_single_iref function in libsimba library prior to SMR Apr-2022 Release 1 allows code execution by remote attacker.

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

Heap-based buffer overflow in the parser_single_iref function of the libsimba library allows remote attackers to execute arbitrary code by overflowing the heap-allocated buffer. This is a critical memory corruption vulnerability in a parsing component.

MitigationUpdate libsimba library to SMR Apr-2022 Release 1 or later to incorporate the patched version that properly validates bounds in the parser_single_iref function.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check Android OS version
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shell
    Affected if The device runs Android 10.0, 11.0, or 12.0 specifically, as these are the only versions listed as affected
  2. Locate libsimba library on the device
    Search for libsimba.so in /system/lib64/, /system/lib/, or within application private directories using 'find / -name libsimba.so 2>/dev/null' via ADB root shell
    Affected if The libsimba library is present on the device, indicating the vulnerable component exists
  3. Determine libsimba library version
    Run 'strings libsimba.so | grep -i version' or check the library's metadata; alternatively, contact the device manufacturer or refer to the SMR (Security Maintenance Release) documentation for the library build date
    Affected if The library version corresponds to a build before the SMR Apr-2022 Release 1 patch, or the exact version cannot be verified against known patched releases
  4. Identify applications using libsimba
    Use 'adb shell dumpsys package' or examine app dependencies to find which applications link against libsimba.so; also check logcat for parser_single_iref activity during media parsing operations
    Affected if Any application on the device uses libsimba to parse untrusted media or content, enabling the overflow trigger condition

A device is affected if it runs Android 10.0, 11.0, or 12.0 and contains a libsimba library version predating the SMR Apr-2022 Release 1 patch, with an application actively using the vulnerable parser_single_iref function.

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 libsimba library to SMR Apr-2022 Release 1 or later to incorporate the patched version that properly validates bounds in the parser_single_iref function.

Recommended fix High confidence

SMR Apr-2022 Release 1 (Security Patch Level April 2022)

  1. Check the current SMR (Samsung Mobile Security) patch level on the Samsung Android device by going to Settings > About Phone > Software Information > Security patch level
  2. Apply the SMR Apr-2022 Release 1 security update or later via Settings > Software Update > Download and Install
  3. Verify the device is running security patch level April 2022 or later after the update completes
Caveat Security updates typically have minimal risk; verify that critical apps are compatible with the April 2022 patch level

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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