dbcve.org
Internet SecurityApplication · Kaspersky

CVE-2017-12817

HIGH · 7.5 CVSS v3.1 Published 2017-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
In Kaspersky Internet Security for Android 11.12.4.1622, some of the application trace files were not encrypted.

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 · low confidence

In Kaspersky Internet Security for Android 11.12.4.1622, certain application trace files were stored without encryption, potentially exposing sensitive operational data to unauthorized access via local file system or device compromise.

MitigationEnable encryption for all trace/log files within the application or upgrade to a patched version that implements proper encryption for trace output.

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
Internet SecurityApplication
Affected:= 11.12.4.1622

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify Kaspersky Internet Security for Android is installed
    Check your device's installed applications list for 'Kaspersky Internet Security' or 'Kaspersky Security'
    Affected if The application is present on the device
  2. Confirm the exact version number
    Go to the app's About or Settings section and note the displayed version number
    Affected if The version is exactly 11.12.4.1622
  3. Locate trace or log files within the app data directory
    Using a file manager with root access or ADB, navigate to /data/data/com.kaspersky.kes/ or /sdcard/Android/data/com.kaspersky.kes/ and look for files with names containing 'trace', 'log', or 'debug' in the files or logs subdirectories
    Affected if Trace or log files exist in the application data directory
  4. Determine if trace files contain unencrypted sensitive data
    Open any found trace or log files in a text viewer and inspect the contents for readable operational data such as network requests, user activity, or system interactions
    Affected if The trace files are stored as plain text and contain readable operational information

You are affected if you have Kaspersky Internet Security for Android version 11.12.4.1622 installed and unencrypted trace/log files exist in the application's data directory.

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

Enable encryption for all trace/log files within the application or upgrade to a patched version that implements proper encryption for trace output.

Fix this in Internet Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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