CVE-2019-2045
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 JSCallTyper of typer.cc, there is an out of bounds write due to an incorrect bounds check. This could lead to remote code execution in the proxy auto-config 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.1 Android-9 Android ID: A-117554758
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 write vulnerability in JSCallTyper of typer.cc within the Chromium component used for proxy auto-config (PAC) handling in Android. The vulnerability stems from an incorrect bounds check that allows writing beyond allocated memory boundaries, enabling remote code execution without user interaction or additional privileges.
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= 7.0= 7.1.1= 7.1.2= 8.1= 9.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check your Android versionGo to Settings > About Phone > Android version. Alternatively, run 'getprop ro.build.version.release' via ADB shell.Affected if The version is 7.0, 7.1.1, 7.1.2, 8.1, or 9.0 - these are the explicitly listed affected versions.
-
Identify the WebView component versionGo to Settings > Apps > Android System WebView (or WebView). Check the version number shown. On some devices, find 'WebView' in the app list and note its version.Affected if The WebView version is unpatched - compare against the Chromium release that fixed CVE-2019-2045 (which was addressed in Chromium 72.0.3626.81 and later, but the specific Android patch level matters more).
-
Verify if Proxy Auto-Config (PAC) is in useCheck your device's Wi-Fi or mobile network proxy settings. PAC is enabled when 'Proxy' is set to 'Auto-config' and a PAC URL or script is specified. On Android 7+, go to Settings > Network & Internet > Wi-Fi > long-press network > Modify network > Advanced options > Proxy.Affected if PAC is actively configured and in use - this vulnerability only affects the PAC handling code path in the Chromium component.
You are affected if your Android version is 7.0, 7.1.1, 7.1.2, 8.1, or 9.0 AND you use Proxy Auto-Config (PAC) with an unpatched WebView/Chromium component.
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 dataUpdate Android to a patched version beyond Android 9, or update the Chromium/WebView component to receive the security fix; this is a Chromium V8 engine vulnerability patched in later Android releases.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2045 — 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-2019-2045 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