# CVE-2009-0066: Security feature bypass in n/a

> Attackers can bypass Intel Trusted Execution Technology loader integrity protections, potentially compromising system security.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 7 Jan 2009
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jg57-33qj-2h37

## What is CVE-2009-0066?

CVE-2009-0066 is a high-severity vulnerability in n/a, published on 7 Jan 2009. 

### Official description

Multiple unspecified vulnerabilities in Intel system software for Trusted Execution Technology (TXT) allow attackers to bypass intended loader integrity protections, as demonstrated by exploitation of tboot.  NOTE: as of 20090107, the only disclosure is a vague pre-advisory with no actionable information. However, because it is from a well-known researcher, it is being assigned a CVE identifier for tracking purposes.

## Which versions are affected by CVE-2009-0066?

It affects 1 product.


Products: Intel Trusted Execution Technology.

## How do I fix CVE-2009-0066?

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

## Is CVE-2009-0066 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0066 and fix it if it is affected.

What it is: CVE-2009-0066 is a high-severity vulnerability in n/a, published on 7 Jan 2009. 
Exploitation: There is no known exploitation of CVE-2009-0066 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-2009-0066/ (Markdown: https://insights.sbomify.com/CVE-2009-0066/index.md)
```

## Sources

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

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