CVE-2022-27567
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 · uneditedNull pointer dereference vulnerability in parser_hvcC function of libsimba library prior to SMR Apr-2022 Release 1 allows out of bounds write by remote attackers.
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 confidenceA null pointer dereference vulnerability in the parser_hvcC function of libsimba library allows remote attackers to achieve out-of-bounds writes by sending specially crafted media data. This parsing vulnerability in H.264/H.265 configuration parsing can lead to arbitrary code execution with critical severity (CVSS 9.8).
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= 10.0= 11.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shellAffected if The device runs Android 10.0, 11.0, or 12.0 exactly (those are the affected versions listed)
-
Identify libsimba library presenceSearch the device filesystem for libsimba.so using 'find / -name libsimba.so 2>/dev/null' via ADB root shell, or inspect APK/ROM files for the libraryAffected if The libsimba library is present on the device
-
Determine libsimba library versionRun 'strings libsimba.so | grep -i version' or check the library's metadata, or look for version strings within the binaryAffected if The library version cannot be determined or is earlier than SMR Apr-2022 Release 1 (the patched version)
-
Verify H.264/H.265 media parsing is in useCheck if any application uses media components that rely on libsimba for H.264/H.265 configuration parsing (hvcC box parsing), or monitor media playback/encoding activityAffected if The device processes H.264/H.265 bitstreams that trigger the parser_hvcC function in libsimba
A device is affected if it runs Android 10.0, 11.0, or 12.0 and contains the libsimba library with a version earlier than SMR Apr-2022 Release 1, and any app processes H.264/H.265 media content.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate libsimba library to SMR Apr-2022 Release 1 or later to obtain the patched version. Identify and update all products and dependencies that incorporate the vulnerable libsimba library.
Samsung SMR Apr-2022 Release 1
- 1. Go to Settings on the Samsung Android device
- 2. Navigate to Settings > Software update or Settings > About phone > Software update
- 3. Check the current Android security patch level under 'Android security patch level'
- 4. Download and install the April 2022 Samsung Security Update (SMR Apr-2022 Release 1) or later
- 5. Verify the update was applied by confirming the security patch level shows April 2022 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27567 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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