CVE-2017-7327
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 · uneditedYandex Browser installer for Desktop before 17.4.1 has a DLL Hijacking Vulnerability because an untrusted search path is used for dnsapi.dll, winmm.dll, ntmarta.dll, cryptbase.dll or profapi.dll.
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 confidenceThe Yandex Browser installer for Desktop versions prior to 17.4.1 is vulnerable to DLL hijacking due to the use of an untrusted search path when loading system DLLs (dnsapi.dll, winmm.dll, ntmarta.dll, cryptbase.dll, profapi.dll). An attacker who can place a malicious DLL in a location the installer searches (such as the current working directory) could achieve code execution with the privileges of the installer process.
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<= 17.4.0.16CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Yandex Browser installationCheck common installation paths such as C:\Program Files\Yandex\YandexBrowser or C:\Users\%username%\AppData\Local\Yandex\YandexBrowser for the presence of the browser executable (browser.exe)Affected if Yandex Browser is not found in either location, the product is not installed and this CVE does not apply
-
Identify installed Yandex Browser versionRight-click browser.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, run: wmic datafile where "name='C:\\Program Files\\Yandex\\YandexBrowser\\browser.exe'" get VersionAffected if The version cannot be determined or the file does not exist
-
Compare version to affected rangeCompare the installed version number to 17.4.0.16. Versions 17.4.0.16 and below (for example 17.4.0.14, 17.3.0.10, 1.5.1.0) are within the vulnerable rangeAffected if The installed version is 17.4.0.16 or lower, indicating the installer used to deploy the browser was vulnerable to DLL hijacking
-
Verify current working directory riskWhen running the Yandex Browser installer in the future, ensure it is executed from a trusted directory (such as the Downloads folder after verification) and not from a location writable by other usersAffected if The installer is run from a directory where an attacker could place malicious dnsapi.dll, winmm.dll, ntmarta.dll, cryptbase.dll, or profapi.dll
A system is affected if Yandex Browser is installed with version 17.4.0.16 or lower, indicating a vulnerable installer (prior to 17.4.1) was used to deploy the browser.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Yandex Browser to version 17.4.1 or later, which contains the patched installer that properly secures the DLL search path.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7327 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-7327 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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