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

> A local attacker in a paravirtualized guest can modify CR4 TSC to crash the host, causing denial of service and potential privilege escalation.

- **Severity:** Medium 4.7 (`AV:L/AC:M/Au:N/C:N/I:N/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:** Yes
- **Published:** 9 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qgxw-cvg4-3v23

## What is CVE-2007-5907?

CVE-2007-5907 is a medium-severity vulnerability in n/a, published on 9 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Xen 3.1.1 does not prevent modification of the CR4 TSC from applications, which allows pv guests to cause a denial of service (crash).

Weakness: CWE-264

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

It affects 1 product.


Products: Xensource Inc Xen.

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

Apply the vendor's patch.

## Is CVE-2007-5907 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4993](https://insights.sbomify.com/CVE-2007-4993/): Command injection in n/a (medium 6.9)
- [CVE-2007-3919](https://insights.sbomify.com/CVE-2007-3919/): Path traversal in n/a (medium 6.0)
- [CVE-2007-5906](https://insights.sbomify.com/CVE-2007-5906/): Denial of service in n/a (medium 4.7)
- [CVE-2008-1619](https://insights.sbomify.com/CVE-2008-1619/): The ssm_i emulation in Xen 5.1 on IA64 architectures allows attackers to cause a denial of service (dom0 panic) via certain traffic, as demo (medium 4.3)
- [CVE-2007-6207](https://insights.sbomify.com/CVE-2007-6207/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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