dbcve.org
AndroidOperating system · Google

CVE-2018-9433

HIGH · 8.8 CVSS v3.1 Published 2024-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 ArrayConcatVisitor of builtins-array.cc, there is a possible type confusion due to improper input validation. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.

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 exists in the ArrayConcatVisitor of V8 JavaScript engine's builtins-array.cc. Improper input validation during array concatenation operations could allow an attacker to execute arbitrary code remotely. User interaction (such as visiting a malicious page) is required for exploitation.

MitigationUpdate Google Chrome or any Chromium-based browser to a version that includes the fix for CVE-2018-9433. Alternatively, update the V8 engine component if embedded in a custom application.

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:= 6.0= 6.0.1= 7.0= 7.1.1= 7.1.2

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify the Android version
    Go to Settings > About Phone (or About Device) > Android version. Alternatively, run `getprop ro.build.version.release` via ADB shell.
    Affected if The device runs Android 6.0, 6.0.1, 7.0, 7.1.1, or 7.1.2 exactly.
  2. Identify the Chrome or WebView version
    Open Chrome, go to chrome://version. For WebView, check the Android System WebView version in Settings > Apps > Android System WebView, or run `getprop com.google.android.webview.version` via ADB shell.
    Affected if The Chrome or WebView version is known and maps to a V8 engine version predating the fix for CVE-2018-9433.
  3. Confirm WebView is in use
    Determine if the application uses Android System WebView (the default Android browser engine) for rendering web content. Check if the affected app is the stock Android Browser or apps embedding WebView.
    Affected if WebView is enabled and used as the rendering engine, and the Android version matches the affected range.
  4. Verify JavaScript is enabled
    In Chrome or the stock Android Browser, ensure JavaScript is enabled in settings. This is typically on by default but can be toggled in browser settings.
    Affected if JavaScript is enabled, as the vulnerability is triggered through malicious JavaScript during array concatenation operations.

A user is affected if their Android device runs version 6.0 through 7.1.2 and uses a Chromium-based browser or WebView with a V8 engine version that predates the CVE-2018-9433 fix.

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

Update Google Chrome or any Chromium-based browser to a version that includes the fix for CVE-2018-9433. Alternatively, update the V8 engine component if embedded in a custom application.

Recommended fix High confidence

Upgrade to Android 8.0 or later, which received the fix through the July 2018 Android Security Bulletin (2018-07-01 patch level)

  1. 1. Identify all devices running Android versions 6.0, 6.0.1, 7.0, or 7.1.1 in your organization
  2. 2. Check if the device manufacturer has released a security update containing the July 2018 Android Security Patch Level for your specific device model
  3. 3. If a security update is available, apply it through the device's system settings > Security > Security patch level
  4. 4. If no update is available from the manufacturer, the device should be retired or isolated from untrusted networks
  5. 5. Until remediation is complete, restrict user access to untrusted web content and disable JavaScript in WebView-based applications where possible
  6. 6. Consider using mobile device management (MDM) solutions to enforce network segmentation for affected devices
Caveat Android 8.0+ may have compatibility issues with older applications or device-specific features; some legacy devices may not support upgrading beyond Android 7.x

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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