# CVE-2013-5740: Security feature bypass in n/a

> Local attackers can bypass Intel Trusted Execution Technology protections and execute unauthorized SINIT ACM functions via unspecified vectors.

- **Severity:** Medium 6.9 (`AV:L/AC:M/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:** 12 Sep 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pw9g-5mm4-5mpm

## What is CVE-2013-5740?

CVE-2013-5740 is a medium-severity vulnerability in n/a, published on 12 Sep 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in the Intel Trusted Execution Technology (TXT) SINIT Authenticated Code Modules (ACM) before 1.2, as used by the Intel QM77, QS77, Q77 Express, C216, Q67 Express, C202, C204, and C206 chipsets and Mobile Intel QM67 and QS67 chipsets, when the measured launch environment (MLE) is invoked, allows local users to bypass the Trusted Execution Technology protection mechanism and perform other unspecified SINIT ACM functions via unspecified vectors.

## Which versions are affected by CVE-2013-5740?

It affects 10 products.


Products: Intel C202 Chipset, Intel C204 Chipset, Intel C206 Chipset, Intel C216 Chipset, Intel Mobile Intel Qm67 Chipset, Intel Mobile Intel Qs67 Chipset, Intel Q67 Express Chipset, Intel Qm77 Chipset, Intel Qs77 Chipset, Intel Trusted Execution Technology Sinit Authenticated Code Module.

## How do I fix CVE-2013-5740?

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

## Is CVE-2013-5740 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5740 and fix it if it is affected.

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

## Sources

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

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