CVE-2019-8285
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 · uneditedKaspersky Lab Antivirus Engine version before 04.apr.2019 has a heap-based buffer overflow vulnerability that potentially allow arbitrary code execution
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 confidenceA heap-based buffer overflow vulnerability exists in Kaspersky Lab Antivirus Engine versions released before April 4, 2019. The vulnerability resides in the antivirus scanning engine and could potentially allow an attacker to achieve arbitrary code execution by exploiting the memory corruption during malicious file processing.
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< 2019.04.04CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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 the installed Kaspersky Antivirus product versionOpen the Kaspersky application interface, navigate to the Help or About section, and locate the version information. Alternatively, check the installed programs list in the operating system's control panel.Affected if The displayed version or build date is earlier than April 4, 2019
-
Identify the Antivirus Engine component versionWithin the Kaspersky product interface, look for engine version or definition date information. This is often visible in Settings, Support, or the main status window. The engine version is separate from the main product version.Affected if The engine version or signature date is before the April 4, 2019 update release
-
Verify if real-time file scanning is enabledOpen Kaspersky settings and check the status of real-time protection or file antivirus scanning. This is typically found under Protection or Scanning settings.Affected if Real-time scanning is active and the engine version is pre-April 4, 2019, as exploitation occurs during file processing
-
Check the installation timestamp of the Kaspersky softwareReview the installation date through the operating system's installed programs list or the program's installation directory metadata.Affected if The software has not been updated since before April 4, 2019
You are affected if your Kaspersky Antivirus Engine version predates April 4, 2019 and real-time file scanning is enabled, allowing malicious file processing to trigger the heap-based buffer overflow.
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 data2019.04.04
Update Kaspersky Lab Antivirus to a version released after April 4, 2019 to incorporate the patched engine components.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8285 — 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-2019-8285 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