dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-13614

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
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
Kaspersky has fixed a security issue in Kaspersky Anti-Virus SDK for Windows, Kaspersky Security for Virtualization Light Agent, Kaspersky Endpoint Security for Windows, Kaspersky Small Office Security, Kaspersky for Windows (Standard, Plus, Premium), Kaspersky Free, Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Security Cloud, Kaspersky Safe Kids, Kaspersky Anti-Ransomware Tool that could allow an authenticated attacker to write data to a limited area outside the allocated kernel memory buffer. The fix was installed automatically for all Kaspersky Endpoint products.

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 kernel memory buffer write vulnerability in multiple Kaspersky products for Windows allows an authenticated attacker to write data beyond the allocated buffer boundary. The issue affects kernel-level memory operations in the antivirus software and has been addressed through automatic updates for Endpoint products.

MitigationEnsure all Kaspersky products are updated to the latest versions. For non-Endpoint products, manually check for and apply available updates. Endpoint products received automatic patches.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/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. Identify installed Kaspersky product
    Open Programs and Features in Windows Control Panel or go to Settings > Apps > Apps & Features to find the installed Kaspersky product name (e.g., Kaspersky Endpoint Security, Kaspersky Anti-Virus, Kaspersky Internet Security)
    Affected if The installed product is any Kaspersky security product for Windows that has not been updated to a patched version
  2. Check installed product version
    Right-click the Kaspersky icon in the system tray, select About, or open the product and navigate to Support > About. Record the version number displayed.
    Affected if The version number is older than the patched version released for this CVE (version information should be obtained from Kaspersky's official security advisory for CVE-2024-13614)
  3. Verify update status
    Open the Kaspersky application, go to Protection or Updates section, and check the last update date and database version. Confirm the antivirus databases are current.
    Affected if The last update was performed before the patch release date for this CVE, or updates show as failed or pending
  4. Check automatic update configuration
    Open Kaspersky settings, look for Updates or Scheduler section, and verify that automatic updates are enabled. For Endpoint products, check the administration console for update policy status.
    Affected if Automatic updates are disabled or the Endpoint management console shows the patch as not applied
  5. Confirm kernel-level protection status
    Open Kaspersky settings and navigate to Protection or Self-Defense sections. Verify that kernel-mode protection components are enabled and running.
    Affected if Kernel-level protection components are enabled (since the vulnerability affects kernel memory operations, the product must have these components running to be vulnerable)

The user is affected if they have any unpatched Kaspersky product for Windows with kernel protection components enabled, where the version has not been updated to include the fix for CVE-2024-13614.

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

Ensure all Kaspersky products are updated to the latest versions. For non-Endpoint products, manually check for and apply available updates. Endpoint products received automatic patches.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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