dbcve.org
AndroidOperating system · Google

CVE-2022-28786

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Improper buffer size check logic in aviextractor 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 confidence

This is an out-of-bounds read vulnerability in the aviextractor library caused by improper buffer size check logic. The missing or inadequate validation allows reading beyond allocated buffer boundaries, which can cause a temporary denial of service. The fix involves adding proper buffer size validation before read operations.

MitigationApply the SMR May-2022 Release 1 patch (or later) which adds proper buffer size check logic to the aviextractor library. Ensure all media file parsing code validates buffer boundaries before performing read operations.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version
    Check the device or system settings to confirm the installed Android OS version is 10.0, 11.0, or 12.0
    Affected if Android version is exactly 10.0, 11.0, or 12.0
  2. Identify aviextractor library presence
    Check if the aviextractor library is present and loaded on the system. This library is typically used for AVI media file extraction and may be found in system media processing components or video player applications
    Affected if The aviextractor library is in use for media file parsing
  3. Confirm patch level
    Check the installed SMR (Security Maintenance Release) patch level. On Android, this can be verified through system security patch settings or by querying the Android build information for the May-2022 security update status
    Affected if The May-2022 SMR1 patch (or later) has NOT been applied and the system remains at the original vulnerable patch level
  4. Check media parsing configuration
    Verify if the aviextractor library is actively parsing media files without proper buffer boundary validation. This may be observable through system logs or media processing activity
    Affected if Media files are being parsed through aviextractor without the buffer validation fix applied

A system is affected if it runs Android 10.0, 11.0, or 12.0 with the aviextractor library in use and lacks the May-2022 SMR1 security patch that adds proper buffer size validation.

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

Apply the SMR May-2022 Release 1 patch (or later) which adds proper buffer size check logic to the aviextractor library. Ensure all media file parsing code validates buffer boundaries before performing read operations.

Recommended fix Moderate confidence

SMR May-2022 Release 1 or later

  1. 1. Identify the Samsung device model number (found in Settings > About Phone)
  2. 2. Check the current Android security patch level (found in Settings > About Phone > Software Information > Security patch level)
  3. 3. Navigate to the Samsung security updates page at security.samsungmobile.com
  4. 4. Locate the SMR (Samsung Monthly Release) for May-2022 Release 1 or later
  5. 5. Apply the latest available system update for the device which includes the May-2022 security patch
  6. 6. Verify the security patch level has been updated to May-2022 or later in Settings > About Phone > Software Information

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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