CVE-2021-0650
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 WT_InterpolateNoLoop of eas_wtengine.c, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-9Android ID: A-190286685
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 confidenceOut-of-bounds read vulnerability in the Android Wavetable (WT) audio engine. The WT_InterpolateNoLoop function in eas_wtengine.c contains an incorrect bounds check, allowing reading beyond allocated buffer boundaries. This leads to remote information disclosure with no additional privileges required, though user interaction (opening a malicious audio file) is needed for exploitation.
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= 9.0= 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 OS versionGo to Settings > About Phone > Android version (or run 'getprop ro.build.version.release' via ADB)Affected if Version equals 9.0, 10.0, or 11.0 exactly
-
Verify wavetable audio library presenceCheck for the presence of libeas_wt.so or similar wavetable library in /system/lib/ or /vendor/lib/ using 'ls /system/lib/libeas_wt*' via ADBAffected if The library file exists on the device
-
Identify apps using wavetable synthesisMonitor audio activity using 'dumpsys audio' or 'ps -A | grep -i audio' to find processes using the WT audio engineAffected if Any application is actively playing audio that uses the wavetable engine (common in MIDI playback apps)
-
Check for malicious audio file processingReview recent media file access logs or use a file integrity scanner to check for recently opened unusual audio filesAffected if A synthesized or MIDI audio file from an untrusted source was recently opened
The environment is affected if the Android device runs version 9.0, 10.0, or 11.0 exactly AND uses any application that processes audio through the Android Wavetable (WT) engine.
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 the official Android security patch for CVE-2021-0650 (Android-9, -10, -11). Users should accept system updates promptly as this vulnerability resides in a system library requiring OS-level patching.
Android 12 or January 2021 Android Security Patch Level
- 1. Check the Android Security Patch Level on the affected device by navigating to Settings > About Phone > Security Patch Level
- 2. Verify the device is not running a version with the January 2021 security patch or earlier
- 3. If available, upgrade the device to Android 12 (which includes the fix for this vulnerability)
- 4. If upgrading to Android 12 is not possible, ensure the device receives the January 2021 Android Security Update or later
- 5. Verify the fix by confirming the Security Patch Level shows January 2021 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0650 — 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-0650 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