Anti VirusApplication · Kaspersky

CVE-2019-15688

MEDIUM · 6.1 CVSS v3.1 Published 2019-11-26
Fix available
A fix is available. Upgrade to after 2020 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Kaspersky Anti-Virus, Kaspersky Internet Security, Kaspersky Total Security, Kaspersky Free Anti-Virus, Kaspersky Small Office Security, Kaspersky Security Cloud up to 2020, the web protection component did not adequately inform the user about the threat of redirecting to an untrusted site. Bypass.

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 confidence

The web protection component in multiple Kaspersky consumer and small business security products (versions up to 2020) failed to adequately inform users about the threat when being redirected to an untrusted site, allowing a bypass of security warnings.

MitigationUpdate affected Kaspersky products to version 2020 or later to receive the patched web protection component that properly warns users about redirects to untrusted sites.

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
Anti VirusApplication
Affected:<= 2020
Internet SecurityApplication
Affected:<= 2020
Security CloudApplication
Affected:<= 2020
Small Office SecurityApplication
Affected:<= 7
Total SecurityApplication
Affected:<= 2020

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 the installed Kaspersky application or go to Programs and Features in Windows to see which Kaspersky product is installed (Anti-Virus, Internet Security, Security Cloud, Small Office Security, or Total Security)
    Affected if The product is one of the listed affected products (Kaspersky Anti-Virus, Internet Security, Security Cloud, Small Office Security, or Total Security)
  2. Check installed version number
    Open the Kaspersky application, go to Settings, and look for the About or Support section which displays the version number; alternatively, right-click the Kaspersky icon in the system tray and select About
    Affected if The version is 2020 or lower for Anti-Virus, Internet Security, Security Cloud, or Total Security; or version 7 or lower for Small Office Security
  3. Confirm web protection is enabled
    Open Kaspersky settings and verify that Web Protection, Web Anti-Virus, or Network Traffic Scanning is turned ON (the exact name varies by product)
    Affected if The web protection component is enabled and active in the product settings
  4. Compare version against affected ranges
    If the exact version is known, compare it to the affected range: any version up to and including 2020 for the 2020-line products, or any version up to and including 7 for Small Office Security
    Affected if The installed version falls within or below the affected version threshold for that product line

You are affected if you have any of the listed Kaspersky products (Anti-Virus, Internet Security, Security Cloud, Small Office Security, or Total Security) at version 2020 or earlier (or Small Office Security 7 or earlier) with the web protection component enabled.

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 2020
Interim mitigation

Update affected Kaspersky products to version 2020 or later to receive the patched web protection component that properly warns users about redirects to untrusted sites.

Fix this in Anti Virus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15688 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15688 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