AndroidOperating system · Google

CVE-2019-2208

HIGH · 7.5 CVSS v3.1 Published 2019-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 PromiseBuiltinsAssembler::NewPromiseCapability of builtins-promise.cc, there is a possible out of bounds read in v8 JIT code due to a bug in code generation. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android-8.1, Android-9 Android ID: A-138441919

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

This is an out-of-bounds read vulnerability in the V8 JavaScript engine's JIT code generation for Promise capabilities. The bug in PromiseBuiltinsAssembler::NewPromiseCapability in builtins-promise.cc allows remote information disclosure by reading memory beyond allocated bounds, without requiring any user interaction or additional execution privileges.

MitigationApply the Android security patch for the A-138441919 vulnerability (included in Android 8.1 and 9 security updates). For applications using WebView, ensure users are on patched Android versions or consider restricting access to sensitive data until devices are updated.

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:= 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version is exactly 9.0 (Android 9 Pie) - other versions are not affected by this specific CVE
  2. Confirm V8 engine usage
    Determine if the target application uses WebView or contains an embedded Chromium-based browser. Check app manifest for android.webkit.WebView usage or inspect the application's bundled libraries for libchromium.so or similar V8-related binaries
    Affected if The application uses WebView or any Chromium-based component that includes the V8 JavaScript engine
  3. Check for Chrome/WebView component versions
    For Chrome: Navigate to chrome://version in the Chrome app. For WebView: Navigate to chrome://inspect/#devices in desktop Chrome with the device connected, or check the WebView implementation in Settings > Apps > Android System WebView (on Android 9.0 this typically shows version 74.x-76.x range)
    Affected if The WebView or Chrome version is from the affected Android 9.0 release (typically unpatched versions from mid-2019)
  4. Verify security patch level
    Check Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The Security Patch Level is earlier than September 2019 (the patch A-138441919 was included in Android 9.0 security updates starting September 2019)

A device or application is affected if running Android 9.0 with an unpatched WebView/Chrome component predating the September 2019 security update.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch for the A-138441919 vulnerability (included in Android 8.1 and 9 security updates). For applications using WebView, ensure users are on patched Android versions or consider restricting access to sensitive data until devices are updated.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-2208 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