dbcve.org
Yandex BrowserApplication · Yandex

CVE-2017-7326

HIGH · 7.5 CVSS v3.0 Published 2018-01-19
Fix available
A fix is available. Upgrade to after 17.4 or later.
See remediation →
82/100
Remediation priority · High
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
Race condition issue in Yandex Browser for Android before 17.4.0.16 allowed a remote attacker to potentially exploit memory corruption 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 · moderate confidence

A race condition vulnerability in Yandex Browser for Android versions prior to 17.4.0.16 allows a remote attacker to exploit memory corruption through a maliciously crafted HTML page. This client-side browser vulnerability can be triggered when a user visits a specially crafted webpage, potentially leading to arbitrary code execution or browser crash.

MitigationUpdate Yandex Browser for Android to version 17.4.0.16 or later. For enterprise environments, deploy the update via mobile device management (MDM) and verify completion across all affected devices.

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:<= 17.4

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

CVSS:3.0/AV:N/AC:H/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. Confirm Yandex Browser is installed
    Navigate to Settings > Apps on the Android device and look for 'Yandex Browser' in the app list, or run 'adb shell pm list packages | grep yandex'
    Affected if The app package 'com.yandex.browser' is present on the device
  2. Retrieve the installed version number
    Open Settings > Apps > Yandex Browser and view the Version information displayed, or run 'adb shell dumpsys package com.yandex.browser | grep versionName'
    Affected if A version number is displayed in the app details
  3. Compare version against affected range
    Check if the installed version is less than 17.4.0.16. The affected version range is any build <= 17.4 (such as 17.4, 17.3.x, 17.2.x, etc.)
    Affected if The installed version is 17.4.0.15 or lower, or any version in the 17.4.x line below 17.4.0.16

The user is affected if Yandex Browser for Android is installed with any version prior to 17.4.0.16.

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 a release after 17.4
Interim mitigation

Update Yandex Browser for Android to version 17.4.0.16 or later. For enterprise environments, deploy the update via mobile device management (MDM) and verify completion across all affected devices.

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-7326 — 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-7326 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