# CVE-2007-1220: Security feature bypass in n/a

> Attackers with physical access can bypass code-signing in the Xbox 360 kernel to execute arbitrary code.

- **Severity:** Medium 6.2 (`AV:L/AC:H/Au:N/C:C/I:C/A:C`)
- **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:** 2 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mr3x-ww57-r38q

## What is CVE-2007-1220?

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

### Official description

The Hypervisor in Microsoft Xbox 360 kernel 4532 and 4548 does not properly verify the parameters passed to the syscall dispatcher, which allows attackers with physical access to bypass code-signing requirements and execute arbitrary code.

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

It affects 1 product.


Products: Microsoft Xbox 360.

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

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

## Is CVE-2007-1220 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1221](https://insights.sbomify.com/CVE-2007-1221/): Security feature bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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