# CVE-2008-5725: Privilege escalation in n/a

> Local attackers can escalate privileges by sending malicious IOCTL requests to the PowerStrip kernel driver, allowing arbitrary memory overwrites.

- **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:** 26 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rg67-pc27-xqp8

## What is CVE-2008-5725?

CVE-2008-5725 is a high-severity vulnerability in n/a, published on 26 Dec 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The NT kernel-mode driver (aka pstrip.sys) 5.0.1.1 and earlier in EnTech Taiwan PowerStrip 3.84 and earlier allows local users to gain privileges via certain IRP parameters in an IOCTL request to \Device\Powerstrip1 that overwrites portions of memory.

Weakness: CWE-264

## Which versions are affected by CVE-2008-5725?

It affects 1 product.


Products: Entechtaiwan Powerstrip.

## How do I fix CVE-2008-5725?

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

## Is CVE-2008-5725 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5725 exists.

Public exploit code:

- PowerStrip 3.84 - 'pstrip.sys' Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5725 and fix it if it is affected.

What it is: CVE-2008-5725 is a high-severity vulnerability in n/a, published on 26 Dec 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5725 exists.

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-2008-5725/ (Markdown: https://insights.sbomify.com/CVE-2008-5725/index.md)
```

## Sources

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

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