CVE-2022-28787
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 buffer size check logic in wmfextractor library prior to SMR May-2022 Release 1 allows out of bounds read leading to possible temporary denial of service. The patch adds buffer size check logic.
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 buffer size check logic in the wmfextractor library allows out-of-bounds memory read access. This occurs when the library processes WMF (Windows Metafile) files without validating buffer boundaries before read operations, potentially causing information disclosure or a temporary denial of service condition.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version displayed is 10.0, 11.0, or 12.0 (exact matches as listed)
-
Verify wmfextractor library presenceCheck for the presence of libwmfextractor.so in /system/lib/ or /vendor/lib/ directories using 'find /system/lib -name libwmfextractor.so' or 'ls -la /system/lib64/libwmf*'Affected if The library file exists on the device, indicating the vulnerable component is present
-
Check Android SMR patch levelRun 'getprop ro.build.version.security_patch' to obtain the security patch dateAffected if The patch level is earlier than May 2022 (SMR May-2022 Release 1 or later contains the fix)
-
Identify WMF processing capabilityCheck if apps or services can process WMF files - review media handling in /system/etc/permissions or check for WMF MIME type registration in the frameworkAffected if WMF file processing is enabled and the wmfextractor library is accessible to applications
A device is affected if it runs Android 10.0, 11.0, or 12.0, contains the wmfextractor library, has WMF processing enabled, and has a security patch level before May 2022.
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 to SMR May-2022 Release 1 or later which includes proper buffer size validation checks before memory read operations.
SMR May-2022 Release 1 or later
- Check the current Samsung security patch level on the device (Settings > Security > Security patch level)
- Navigate to Settings > Software Update and download/install the SMR May-2022 Release 1 update or later
- After installation, verify the security patch level reflects May-2022 or later in Settings > Security > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28787 — 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-28787 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