dbcve.org
ChromeWeb browser · Google

CVE-2024-3156

HIGH · 8.8 CVSS v3.1 Published 2024-04-06
Fix available
A fix is available. Upgrade to 123.0.6312.105 or later.
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
Inappropriate implementation in V8 in Google Chrome prior to 123.0.6312.105 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

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 vulnerability in the V8 JavaScript engine in Google Chrome prior to version 123.0.6312.105 allows a remote attacker to perform out-of-bounds memory access via a crafted HTML page. The issue stems from an inappropriate implementation in the V8 engine that does not properly bounds-check memory operations, potentially allowing memory corruption and potentially arbitrary code execution.

MitigationUpdate Google Chrome to version 123.0.6312.105 or later. Organizations should deploy the update through their standard patch management processes and verify that Chromium-based alternative browsers are also updated if used.

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
ChromeWeb browser
Affected:< 123.0.6312.105

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. Verify Google Chrome is installed
    Check for Chrome installation: On Windows look for Chrome in Program Files or check the registry. On macOS check /Applications/Google Chrome.app. On Linux run 'which google-chrome' or 'which chromium'.
    Affected if Chrome is not found on the system, then this CVE does not apply.
  2. Determine installed Chrome version
    Access chrome://version in the browser address bar, or run 'google-chrome --version' (Linux) or 'chromium --version' (Linux). On Windows, right-click chrome.exe and select Properties > Details > File version.
    Affected if Unable to determine version - further investigation needed.
  3. Compare version against affected range
    Parse the installed version number and compare numerically to 123.0.6312.105. Note that versions like 123.0.6312.104, 123.0.6312.80, 122.0.6261.69 are all below the fixed version.
    Affected if Installed version is less than 123.0.6312.105 (for example 123.0.6312.104, 122.x, 121.x, etc.)
  4. Confirm V8 engine is in use
    The V8 JavaScript engine is built into Google Chrome and cannot be disabled through user settings. No manual check needed - it is always active when Chrome runs.
    Affected if Chrome is running - V8 is automatically loaded and this vulnerability is reachable.

If Google Chrome is installed and its version is below 123.0.6312.105, the environment is affected by this vulnerability.

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
Upgrade available Upgrade to 123.0.6312.105 or later
Fixed in 123.0.6312.105
Interim mitigation

Update Google Chrome to version 123.0.6312.105 or later. Organizations should deploy the update through their standard patch management processes and verify that Chromium-based alternative browsers are also updated if used.

Recommended fix High confidence

Chrome 123.0.6312.105 or later

  1. Open Google Chrome browser
  2. Navigate to Settings (three-dot menu) > Help > About Google Chrome
  3. Chrome will automatically check for updates and display the current version
  4. If an update is available, Chrome will download and install it automatically
  5. Restart the browser after the update completes to apply the fix

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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