# CVE-2003-1233: Security feature bypass in n/a

> Privileged attackers can bypass file access restrictions in the Windows kernel driver to access physical memory or drives via symbolic links.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-qf6r-hr4r-92vr

## What is CVE-2003-1233?

CVE-2003-1233 is a critical vulnerability in n/a, published on 28 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pedestal Software Integrity Protection Driver (IPD) 1.3 and earlier allows privileged attackers, such as rootkits, to bypass file access restrictions to the Windows kernel by using the NtCreateSymbolicLinkObject function to create a symbolic link to (1) \Device\PhysicalMemory or (2) to a drive letter using the subst command.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2003-1233?

It affects 1 product.


Products: Pedestalsoftware Integrity Protection Driver.

## How do I fix CVE-2003-1233?

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

## Is CVE-2003-1233 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1233 and fix it if it is affected.

What it is: CVE-2003-1233 is a critical vulnerability in n/a, published on 28 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-1233 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-2003-1233/ (Markdown: https://insights.sbomify.com/CVE-2003-1233/index.md)
```

## Sources

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

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