# CVE-2007-5633: Privilege escalation in n/a

> Local attackers can exploit SpeedFan driver IOCTLs to read/write arbitrary MSRs, enabling privilege escalation and loading of unsigned drivers on Windows Vista x64.

- **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:** 23 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x4vw-hwxw-9rqp

## What is CVE-2007-5633?

CVE-2007-5633 is a high-severity vulnerability in n/a, published on 23 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Speedfan.sys in Alfredo Milani Comparetti SpeedFan 4.33, when used on Microsoft Windows Vista x64, allows local users to read or write arbitrary MSRs, and gain privileges and load unsigned drivers, via the (1) IOCTL_RDMSR 0x9C402438 and (2) IOCTL_WRMSR 0x9C40243C IOCTLs to \Device\speedfan, as demonstrated by an IOCTL_WRMSR action on MSR_LSTAR.

## Which versions are affected by CVE-2007-5633?

It affects 1 product.


Products: Almico Speedfan.

## How do I fix CVE-2007-5633?

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

## Is CVE-2007-5633 being exploited?

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

Public exploit code:

- SpeedFan - 'Speedfan.sys' Local Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-28175](https://insights.sbomify.com/CVE-2020-28175/): Privilege escalation in n/a (high 7.8)
- [CVE-2007-5634](https://insights.sbomify.com/CVE-2007-5634/): Memory corruption in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5633 and fix it if it is affected.

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

## Sources

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

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