dbcve.org
ChromeWeb browser · Google

CVE-2018-6130

MEDIUM · 6.5 CVSS v3.0 Published 2019-06-27
Fix available
A fix is available. Upgrade to 67.0.3396.62 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Incorrect handling of object lifetimes in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.

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

Memory safety vulnerability in WebRTC's object lifetime handling in Google Chrome prior to 67.0.3396.62 allows out-of-bounds memory access via malicious HTML. The incorrect object lifetime management can lead to use-after-free or similar memory corruption conditions exploitable by remote attackers.

MitigationUpdate Google Chrome to version 67.0.3396.62 or later. If WebRTC is used in custom applications, review and validate object lifecycle management in WebRTC implementations.

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:< 67.0.3396.62

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Determine Google Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' / 'chrome --version' from command line
    Affected if version is lower than 67.0.3396.62
  2. Confirm WebRTC module status
    In Chrome, navigate to chrome://webrtc-internals to access WebRTC internals page - this confirms WebRTC is enabled and active
    Affected if WebRTC internals page loads and shows active peer connections or statistics
  3. Check for WebRTC usage in custom applications
    Review any custom applications or browser-based applications that integrate Chrome's WebRTC implementation - check application logs and runtime configurations
    Affected if custom applications use WebRTC APIs and Chrome version is below 67.0.3396.62

Your environment is affected if you are running any version of Google Chrome prior to 67.0.3396.62 and WebRTC is enabled or used by applications in your environment.

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

Update Google Chrome to version 67.0.3396.62 or later. If WebRTC is used in custom applications, review and validate object lifecycle management in WebRTC implementations.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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