# CVE-2010-2031: Memory corruption in n/a

> Local attackers can overwrite kernel memory via a crafted IOCTL request in Kingsoft Webshield, leading to privilege escalation or code execution.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 24 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jf64-vfp6-7x6v

## What is CVE-2010-2031?

CVE-2010-2031 is a high-severity memory corruption vulnerability in n/a, published on 24 May 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

KAVSafe.sys 2010.4.14.609 and earlier, as used in Kingsoft Webshield 3.5.1.2 and earlier, allows local users to overwrite arbitrary kernel memory via a crafted request to IOCTL 0x830020d4 on the KAVSafe device.

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

## Which versions are affected by CVE-2010-2031?

It affects 1 product.


Products: Kingsoft Webshield.

## How do I fix CVE-2010-2031?

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

## Is CVE-2010-2031 being exploited?

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

Public exploit code:

- Kingsoft Webshield 'KAVSafe.sys' 2010.4.14.609 (2010.5.23) - Kernel Mode Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2031 and fix it if it is affected.

What it is: CVE-2010-2031 is a high-severity memory corruption vulnerability in n/a, published on 24 May 2010. 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-2010-2031 in the wild and no public exploit code.

Affected product: n/a. 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-2010-2031/ (Markdown: https://insights.sbomify.com/CVE-2010-2031/index.md)
```

## Sources

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

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