# CVE-2019-9729: Integer overflow in n/a

> A local attacker can exploit an integer signedness error in the SdoKeyCrypt.sys driver to achieve privilege escalation to SYSTEM.

- **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:** 12 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2cjm-39g8-5fv8

## What is CVE-2019-9729?

CVE-2019-9729 is a high-severity vulnerability in n/a, published on 12 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Shanda MapleStory Online V160, the SdoKeyCrypt.sys driver allows privilege escalation to NT AUTHORITY\SYSTEM because of not validating the IOCtl 0x8000c01c input value, leading to an integer signedness error and a heap-based buffer underflow.

Weakness: CWE-787 (Out-of-bounds Write), CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2019-9729?

It affects 1 product.


Products: Shanda Maplestory Online.

## How do I fix CVE-2019-9729?

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

## Is CVE-2019-9729 being exploited?

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

Public exploit code:

- CVE-2019-9729. Transferred from https://github.com/DoubleLabyrinth/SdoKeyCrypt-sys-local-privilege-elevation (github_poc): https://github.com/HyperSine/SdoKeyCrypt-sys-local-privilege-elevation
- CVE-2019-9729. Transferred from https://github.com/DoubleLabyrinth/SdoKeyCrypt-sys-local-privilege-elevation (github_poc): https://github.com/recozone/HyperSine

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9729 and fix it if it is affected.

What it is: CVE-2019-9729 is a high-severity vulnerability in n/a, published on 12 Mar 2019. 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-2019-9729 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-2019-9729/ (Markdown: https://insights.sbomify.com/CVE-2019-9729/index.md)
```

## Sources

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

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