dbcve.org
ChromeWeb browser · Google

CVE-2017-5061

MEDIUM · 5.3 CVSS v3.1 Published 2017-10-27
Fix available
A fix is available. Upgrade to 58.0.3029.81 or later.
See remediation →
60/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
A race condition in navigation in Google Chrome prior to 58.0.3029.81 for Linux, Windows, and Mac allowed a remote attacker to spoof the contents of the Omnibox (URL bar) 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

A race condition in Google Chrome's navigation handling allows a remote attacker to manipulate the Omnibox (URL bar) display through a crafted HTML page. This enables URL spoofing where the displayed URL differs from the actual page being visited, potentially tricking users into believing they're on a legitimate site.

MitigationUpdate Google Chrome to version 58.0.3029.81 or later to patch the navigation race condition vulnerability.

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:< 58.0.3029.81
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/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. Check Google Chrome version on Linux
    Open terminal and run: google-chrome --version or chrome --version or /opt/google/chrome/google-chrome --version
    Affected if Version number is less than 58.0.3029.81
  2. Check Google Chrome version on Windows
    Open Chrome, click menu > Help > About Google Chrome, or run 'google-chrome --version' in Command Prompt
    Affected if Version number is less than 58.0.3029.81
  3. Check Google Chrome version on macOS
    Open Chrome, click Chrome menu > About Google Chrome, or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' in Terminal
    Affected if Version number is less than 58.0.3029.81
  4. Check for Chrome installation on Red Hat Enterprise Linux 6.0
    Run: rpm -qa | grep -i chrome on RHEL Desktop/Server/Workstation 6.0
    Affected if Chrome is installed and version is less than 58.0.3029.81

Your environment is affected if Google Chrome is installed and its version is lower than 58.0.3029.81, particularly on RHEL 6.0 systems where Chrome may be bundled.

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 58.0.3029.81 or later
Fixed in 58.0.3029.81
Interim mitigation

Update Google Chrome to version 58.0.3029.81 or later to patch the navigation race condition vulnerability.

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-2017-5061 — 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-2017-5061 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