# CVE-2009-1123: Microsoft Windows Improper Input Validation

> Local attackers can gain elevated privileges by exploiting improper validation of kernel object changes in Microsoft Windows.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2009
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-gwqf-cc2p-xjrw

## What is CVE-2009-1123?

CVE-2009-1123 is a high-severity vulnerability in Microsoft Windows 2000, published on 10 Jun 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The kernel in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP2, Vista Gold, SP1, and SP2, and Server 2008 SP2 does not properly validate changes to unspecified kernel objects, which allows local users to gain privileges via a crafted application, aka "Windows Kernel Desktop Vulnerability."

## Which versions are affected by CVE-2009-1123?

It affects 5 products.


Products: Microsoft Windows 2000, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2009-1123?

No fix has been published for CVE-2009-1123 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2009-1123 being exploited?

Yes. Attackers have exploited CVE-2009-1123 in the wild since at least 3 Mar 2022.

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2008-4250](https://insights.sbomify.com/CVE-2008-4250/): Microsoft Windows Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2010-0232](https://insights.sbomify.com/CVE-2010-0232/): Microsoft Windows Kernel Exception Handler (high 7.8, exploited in the wild)
- [CVE-2002-0367](https://insights.sbomify.com/CVE-2002-0367/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2010-0269](https://insights.sbomify.com/CVE-2010-0269/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0231](https://insights.sbomify.com/CVE-2010-0231/): Weak cryptography in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1123 and fix it if it is affected.

What it is: CVE-2009-1123 is a high-severity vulnerability in Microsoft Windows 2000, published on 10 Jun 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2009-1123 in the wild since at least 3 Mar 2022.

Affected product: Microsoft Windows 2000. 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-2009-1123/ (Markdown: https://insights.sbomify.com/CVE-2009-1123/index.md)
```

## Sources

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

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