dbcve.org
AndroidOperating system · Google

CVE-2019-2130

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-20
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 CompilationJob::FinalizeJob of compiler.cc, there is a possible remote code execution due to type confusion. This could lead to escalation of privilege from a malicious proxy configuration with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9. Android ID: A-132073833.

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

A type confusion vulnerability in CompilationJob::FinalizeJob in Android's compiler component (compiler.cc) allows remote code execution via a malicious proxy configuration. The flaw enables privilege escalation without requiring additional user privileges or interaction, and can be exploited remotely through network interception.

MitigationApply the Android security patch for this CVE (part of the affected Android security bulletin). For developers building custom ROMs or Android-based products, patch the compiler.cc file to add proper type validation in CompilationJob::FinalizeJob before the vulnerable code path is reached.

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:= 7.0= 7.1.1= 7.1.2= 8.0= 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
    Run 'getprop ro.build.version.release' via ADB shell, or check Settings > About Phone > Android version
    Affected if The version equals 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0 exactly
  2. Verify ART compiler component is present
    Check for the existence of the ART (Android Runtime) compiler binary in /system/bin/ or libraries in /system/lib/ - look for files like art, artd, or libart*.so
    Affected if The Android Runtime compiler component exists and is accessible on the device
  3. Inspect proxy configuration
    Check device proxy settings: run 'settings get global http_proxy' via ADB, or check in Settings > Network & Internet > Wi-Fi (modify network > advanced options)
    Affected if A proxy is configured (non-empty proxy host:port) - the vulnerability is triggered through malicious proxy configuration manipulation

The device is affected if it runs any of the affected Android versions (7.0 through 9.0) and has the compiler component present with an active proxy configuration that could be intercepted.

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 Android security patch for this CVE (part of the affected Android security bulletin). For developers building custom ROMs or Android-based products, patch the compiler.cc file to add proper type validation in CompilationJob::FinalizeJob before the vulnerable code path is reached.

Recommended fix High confidence

Android 9 (Pie) or later with February 2020 security patch level

  1. 1. Navigate to Settings > System > Software Update on the Android device
  2. 2. Check for available system updates
  3. 3. Download and install the latest available Android security patch level
  4. 4. Ensure the device updates to Android 9 (Pie) or later, which contains the fix for this vulnerability
  5. 5. After update, verify the Android security patch level is February 2020 or later in Settings > System > About Phone > Security Patch Level
Caveat Upgrading major Android versions may cause compatibility issues with older apps or result in data loss if not backed up properly; some device features may change

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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