CVE-2022-27573
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 · uneditedImproper input validation vulnerability in parser_infe and sheifd_find_itemIndexin fuctions of libsimba library prior to SMR Apr-2022 Release 1 allows out of bounds write by privileged 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 confidenceImproper input validation in the parser_infe and sheifd_find_itemIndexin functions of the libsimba library allows privileged attackers to perform out-of-bounds memory writes by supplying malicious input to these parsing functions.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 and contains the vulnerable libsimba library
-
Locate libsimba library on the deviceRun 'find /system -name libsimba.so' via ADB shell to locate the library fileAffected if The library file libsimba.so exists in /system/lib or /system/lib64 directories
-
Check library file version metadataRun 'ls -la /system/lib64/libsimba.so' or 'ls -la /system/lib/libsimba.so' via ADB shell to check file timestamps and version infoAffected if The library was built before the SMR Apr-2022 Release 1 patch date
-
Verify vulnerable parsing functions are presentRun 'strings /system/lib64/libsimba.so | grep -E "parser_infe|sheifd_find_itemIndexin"' via ADB shell to confirm the vulnerable function names exist in the binaryAffected if The output shows the strings 'parser_infe' or 'sheifd_find_itemIndexin' indicating the unpatched function names are present in the library
A device is affected if it runs Android 10.0, 11.0, or 12.0 and contains the libsimba.so library with the vulnerable parser_infe and sheifd_find_itemIndexin functions present in the binary.
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 the libsimba library to the SMR Apr-2022 Release 1 or later, which contains the proper input validation fixes for both affected functions.
SMR Apr-2022 Release 1
- Navigate to Settings > Software update on the Samsung device
- Check for and install the SMR (Samsung Maintenance Release) Apr-2022 Update 1 or later
- After installation, verify the patch level is SMR Apr-2022 Release 1 or higher in Settings > About phone > Software information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27573 — 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-27573 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