dbcve.org
Yandex BrowserApplication · Yandex

CVE-2017-7325

HIGH · 7.5 CVSS v3.0 Published 2018-01-19
Fix available
A fix is available. Upgrade to 16.9.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Yandex Browser before 16.9.0 allows remote attackers to spoof the address bar via window.open.

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 · moderate confidence

Yandex Browser before version 16.9.0 contains a vulnerability in the window.open() JavaScript function that allows remote attackers to manipulate the address bar display, enabling URL spoofing attacks where malicious sites can appear to show a legitimate URL.

MitigationUpgrade Yandex Browser to version 16.9.0 or later to obtain the vendor patch. Consider implementing browser version compliance controls in the enterprise environment.

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
Yandex BrowserApplication
Affected:< 16.9.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Identify if Yandex Browser is installed
    Check for Yandex Browser executable in common installation paths: %ProgramFiles%\Yandex\YandexBrowser\Application\browser.exe (Windows) or /Applications/Yandex Browser.app (macOS). On Linux, check /usr/bin/yandex-browser or /opt/yandex/browser/.
    Affected if Yandex Browser executable is found on the system
  2. Determine installed Yandex Browser version (Windows)
    Right-click the Yandex Browser shortcut or executable, select Properties, then look at the Details tab for the Product version field.
    Affected if Version number displayed is below 16.9.0 (for example, 16.7.0, 16.8.1, etc.)
  3. Determine installed Yandex Browser version (via browser UI)
    Open Yandex Browser, type 'chrome://settings' in the address bar, scroll to the bottom and click 'About Yandex Browser' to view the current version number.
    Affected if Version displayed is below 16.9.0
  4. Compare version against affected range
    Document the exact version number found and compare it to the affected range: any version less than 16.9.0 is considered vulnerable to the URL spoofing flaw.
    Affected if Installed version is less than 16.9.0 (for example, 16.8.1, 16.7.0, or earlier)
  5. Confirm vulnerability scope
    Understand that the vulnerability exists in the window.open() JavaScript function which allows URL spoofing. This affects any user who can open arbitrary web pages in the affected browser version.
    Affected if Browser version is below 16.9.0 and users can browse the web

A system is affected if Yandex Browser version is installed and the version number is less than 16.9.0.

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

Upgrade Yandex Browser to version 16.9.0 or later to obtain the vendor patch. Consider implementing browser version compliance controls in the enterprise environment.

Fix this in Yandex Browser 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-7325 — 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-7325 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