dbcve.org
AndroidOperating system · Google

CVE-2019-2007

CRITICAL · 9.8 CVSS v3.0 Published 2019-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In getReadIndex and getWriteIndex of FifoControllerBase.cpp, there is a possible out-of-bounds write due to an integer overflow. This could lead to local escalation of privilege in the audio server with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.1 Android-9Android ID: A-120789744

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 confidence

Integer overflow in getReadIndex and getWriteIndex functions of FifoControllerBase.cpp allows out-of-bounds write operations in the Android audio server. This occurs when index calculations exceed expected integer bounds, enabling local privilege escalation without user interaction.

MitigationApply Android security patches for Android 8.1 and 9 that address A-120789744. If patching is not immediately possible, restrict access to audio server interfaces and monitor for unusual audio service behavior.

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:= 8.1= 9.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check Android version
    View the Android version in Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 8.1 or 9.0 exactly
  2. Verify audio server is running
    Run 'ps -A | grep audio' or 'dumpsys audio' via ADB to confirm audioflinger or audioserver processes are active
    Affected if Audio server processes are running on an affected Android version
  3. Confirm security patch level
    Run 'getprop ro.build.version.security_patch' via ADB to check the installed security patch date
    Affected if Security patch level is earlier than the fix for A-120789744 (Google Android 8.1 and 9.0 patches)
  4. Check for vulnerable audio FIFO controller
    Inspect /system/lib/libaudiofoundation.so or /vendor/lib/libaudiofoundation.so using 'ls -la' via ADB; the vulnerable code resides in FifoControllerBase.cpp within this library
    Affected if The library exists and the Android version is unpatched 8.1 or 9.0

A device is affected if it runs Android 8.1 or 9.0 exactly and lacks the corresponding security patch for vulnerability A-120789744.

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 Android security patches for Android 8.1 and 9 that address A-120789744. If patching is not immediately possible, restrict access to audio server interfaces and monitor for unusual audio service behavior.

Recommended fix High confidence

Android 10 (API 29) or later, or March 2019 Android Security Patch Level

  1. Check current Android version and security patch level in Settings > About Phone > Android version
  2. Verify the device manufacturer provides monthly security updates
  3. If on Android 8.1 or 9.0, upgrade to Android 10 or later which contains the fix for this vulnerability
  4. Alternatively, apply the March 2019 Android Security Patch Level (SPL) or later which includes the fix for CVE-2019-2007
  5. After update, verify fix by confirming the security patch level includes the March 2019 bulletin
Caveat Minimal risk - standard Android upgrade; some legacy apps may have compatibility issues but security fix outweighs risks

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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