CVE-2020-0314
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 AudioService, there are missing permission checks. This could lead to local information disclosure of audio configuration with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-154934920
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 AudioService on Android 11, missing permission checks allow any local application to access audio configuration information without proper authorization. An attacker can exploit this by running a malicious app that queries AudioService APIs to retrieve sensitive audio settings and configuration data.
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= 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.
-
Verify Android version is 11.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Android version is exactly 11.0 (this is the only affected version per the CVE)
-
Confirm AudioService is accessible to appsInspect app permissions via Settings > Apps > [app] > Permissions. Check if apps can access AudioService APIs without android.permission.MODIFY_AUDIO_SETTINGS or equivalent permissionAffected if Any installed application can query AudioService for audio configuration data without holding required permissions
-
Identify apps with audio configuration accessRun 'dumpsys audio' via ADB shell to see which apps have accessed audio service. Cross-reference with installed apps list from 'pm list packages'Affected if Applications without proper audio permissions appear in the audio service access logs or dumpsys output
-
Check for unauthorized audio configuration queriesReview logcat output for AudioService API calls: 'logcat | grep -i AudioService' to identify apps querying audio configurationAffected if Apps without MODIFY_AUDIO_SETTINGS permission are making successful queries to AudioService configuration methods
User is affected if running Android 11.0 AND any application can access AudioService configuration APIs without holding the android.permission.MODIFY_AUDIO_SETTINGS permission.
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.
From vendor dataApply the vendor/security patch from Google for CVE-2020-0314. For custom ROMs or AOSP-based builds, add appropriate permission checks to AudioService methods that expose audio configuration data.
- 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-2020-0314 — 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-2020-0314 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