# CVE-2017-12823: Memory corruption in Kaspersky Embedded Systems Security

> Local attackers can exploit kernel pool memory corruption in Kaspersky Embedded Systems Security to escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 8 Dec 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4j4r-f2wr-q63c

## What is CVE-2017-12823?

CVE-2017-12823 is a high-severity memory corruption vulnerability in Kaspersky Embedded Systems Security, published on 8 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kernel pool memory corruption in one of drivers in Kaspersky Embedded Systems Security version 1.2.0.300 leads to local privilege escalation.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-12823?

It affects 1 product.


Products: Kaspersky Embedded Systems Security.

## How do I fix CVE-2017-12823?

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

## Is CVE-2017-12823 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12823 and fix it if it is affected.

What it is: CVE-2017-12823 is a high-severity memory corruption vulnerability in Kaspersky Embedded Systems Security, published on 8 Dec 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-2017-12823 in the wild and no public exploit code.

Affected product: Kaspersky Embedded Systems 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-2017-12823/ (Markdown: https://insights.sbomify.com/CVE-2017-12823/index.md)
```

## Sources

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

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