CVE-2021-0622
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 · uneditedIn asf extractor, there is a possible out of bounds read due to a heap buffer overflow. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05489178; Issue ID: ALPS05561388.
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 confidenceIn the ASF (Advanced Systems Format) extractor, a heap buffer overflow allows an out-of-bounds read, leading to local information disclosure. The vulnerability requires no user interaction or elevated privileges to exploit. This appears to be in a media processing component, likely on Android/embedded systems based on the ALPS patch identifiers.
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.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version is 10.0 or 11.0 exactly
-
Verify ASF extractor availabilityCheck for the presence of ASF support in the media framework - look for ASF-related libraries or extractor modules in /system/lib/ or /vendor/lib/Affected if ASF media extraction capability is present on the device
-
Identify media processing componentsList installed media codecs and extractors using 'dumpsys media.codec' or 'dumpsys media.extractor' commandsAffected if An ASF extractor component is registered and available
-
Confirm vulnerable componentCheck if the device has not received the ALPS05489178 patch by reviewing the security patch level via 'getprop ro.build.version.security_patch'Affected if Security patch level is earlier than the fix date for ALPS05489178
A user is affected if the device runs Android 10.0 or 11.0, contains an ASF media extractor, and lacks the vendor-specific patch ALPS05489178.
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 · scopedApply vendor patch ALPS05489178 to address the heap buffer overflow in the ASF extractor. This is a bounds-checking fix in the media parsing logic.
Latest Android security patch level for Android 10.0/11.0 (manufacturer-specific)
- Check if your device manufacturer has released a security update for Android 10.0 or 11.0 that includes the MediaTek patch ALPS05489178
- Apply the latest available Android security patch update from your device manufacturer
- Verify the security patch level in Settings > About Phone > Security Patch Level reflects a date after the vulnerability disclosure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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,768.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0622 — 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-2021-0622 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