dbcve.org
Yandex BrowserApplication · Yandex

CVE-2016-8503

HIGH · 7.3 CVSS v3.0 Published 2016-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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 Protect Anti-phishing warning in Yandex Browser for desktop from version 16.7 to 16.9 could be used by remote attacker for brute-forcing passwords from important web-resource with special JavaScript.

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's anti-phishing warning mechanism (versions 16.7-16.9) can be abused by remote attackers via special JavaScript to brute-force passwords from targeted web resources.

MitigationUpdate Yandex Browser to a version beyond 16.9 where the vulnerability has been patched by the vendor.

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.7.0.3342= 16.7.1.20808= 16.9.1.1131

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
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 Yandex Browser is installed
    Check for Yandex Browser installation by looking for the executable (typically in Program Files\Yandex\YandexBrowser\Application\browser.exe on Windows, or via 'ls /Applications | grep -i yandex' on macOS)
    Affected if Yandex Browser is not found on the system - user is not affected
  2. Determine installed Yandex Browser version
    Open Yandex Browser, click the menu (three dots) > Help > About Yandex Browser, or navigate to chrome://version in the address bar to view the full version string
    Affected if The version matches 16.7.0.3342, 16.7.1.20808, or 16.9.1.1131 exactly
  3. Confirm anti-phishing protection is enabled
    Navigate to Settings > Security (or type chrome://settings/security in the address bar) and check if 'Protect you from dangerous sites' or similar anti-phishing protection is turned ON
    Affected if Anti-phishing protection is enabled - the vulnerable feature is active; if disabled, the brute-force abuse cannot be exploited

User is affected if Yandex Browser is installed with version 16.7.0.3342, 16.7.1.20808, or 16.9.1.1131 AND the anti-phishing protection feature is enabled in settings.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Yandex Browser to a version beyond 16.9 where the vulnerability has been patched by the vendor.

Fix this in Yandex Browser Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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