CVE-2018-6306
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 · uneditedUnauthorized code execution from specific DLL and is known as DLL Hijacking attack in Kaspersky Password Manager versions before 8.0.6.538.
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 confidenceKaspersky Password Manager before version 8.0.6.538 is vulnerable to DLL hijacking, where the application loads a specific DLL from an untrusted location, allowing attackers to execute arbitrary code with the privileges of the running application.
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< 8.0.6.538CVSS 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.
-
Confirm Kaspersky Password Manager is installedOpen Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Kaspersky Password Manager' in the list of installed softwareAffected if Kaspersky Password Manager appears in the installed programs list
-
Find the installed version of Kaspersky Password ManagerRight-click the Kaspersky Password Manager shortcut, select 'Properties', then check the 'Details' tab for the product version, or check the version in Help > About within the applicationAffected if A version number is returned showing the installed build
-
Compare installed version to the affected rangeCompare the discovered version number to 8.0.6.538. Versions below 8.0.6.538 (such as 8.0.5.x, 8.0.4.x, etc.) are affectedAffected if The installed version is less than 8.0.6.538 (for example, 8.0.5.1234 or any 8.0.x version prior to 8.0.6.538)
-
Check for legacy or bundled installationsSearch for older Kaspersky Password Manager installations in common program directories (C:\Program Files\Kaspersky Lab\Kaspersky Password Manager or C:\Program Files (x86)\Kaspersky Lab\Kaspersky Password Manager) and check the version of the main executableAffected if Multiple or legacy installations exist with version numbers below 8.0.6.538
The environment is affected if Kaspersky Password Manager is installed with any version lower than 8.0.6.538, as the DLL hijacking vulnerability exists in all prior versions.
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 data8.0.6.538
Update Kaspersky Password Manager to version 8.0.6.538 or later to remediate the DLL hijacking vulnerability.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6306 — 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-2018-6306 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