# CVE-2016-4306: Information disclosure in Total Security

> An unprivileged user can trigger an information leak in the Kaspersky KLDISK driver to expose kernel memory, aiding in bypassing security mitigations.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7x8h-p499-xj9p

## What is CVE-2016-4306?

CVE-2016-4306 is a medium-severity vulnerability in Kaspersky Total Security, published on 6 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple information leaks exist in various IOCTL handlers of the Kaspersky Internet Security KLDISK driver. Specially crafted IOCTL requests can cause the driver to return out-of-bounds kernel memory, potentially leaking sensitive information such as privileged tokens or kernel memory addresses that may be useful in bypassing kernel mitigations. An unprivileged user can run a program from user-mode to trigger this vulnerability.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-4306?

It affects 1 product.


Products: Kaspersky Total Security.

## How do I fix CVE-2016-4306?

No fix has been published for CVE-2016-4306 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-4306 being exploited?

There is no known exploitation of CVE-2016-4306 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4306 and fix it if it is affected.

What it is: CVE-2016-4306 is a medium-severity vulnerability in Kaspersky Total Security, published on 6 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-4306 in the wild and no public exploit code.

Affected product: Kaspersky Total Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-4306/ (Markdown: https://insights.sbomify.com/CVE-2016-4306/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-4306
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-4306
- OSV: https://osv.dev/vulnerability/CVE-2016-4306

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-4306/
Summaries are generated and may contain mistakes; the official description above is the record.