# CVE-2002-2127: Security feature bypass in n/a

> Local privileged attackers can bypass IPD restrictions via symlinks to overwrite kernel memory, enabling privilege escalation.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4mpf-cq6q-387v

## What is CVE-2002-2127?

CVE-2002-2127 is a low-severity vulnerability in n/a, published on 16 Nov 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integrity Protection Driver (IPD) 1.2 and earlier blocks access to \Device\PhysicalMemory by its name, which could allow local privileged processes to overwrite kernel memory by accessing the device through a symlink.

## Which versions are affected by CVE-2002-2127?

It affects 1 product.


Products: Pedestal Software Integrity Protection Driver.

## How do I fix CVE-2002-2127?

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

## Is CVE-2002-2127 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2126](https://insights.sbomify.com/CVE-2002-2126/): Security feature bypass in n/a (low 2.1)
- [CVE-2003-1246](https://insights.sbomify.com/CVE-2003-1246/): Path traversal in n/a (low 2.1)
- [CVE-2004-1718](https://insights.sbomify.com/CVE-2004-1718/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2127 and fix it if it is affected.

What it is: CVE-2002-2127 is a low-severity vulnerability in n/a, published on 16 Nov 2005. 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-2002-2127 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-2002-2127/ (Markdown: https://insights.sbomify.com/CVE-2002-2127/index.md)
```

## Sources

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

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