CVE-2013-5740
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnspecified 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a local privilege bypass vulnerability in Intel Trusted Execution Technology (TXT) SINIT Authenticated Code Modules. The vulnerability allows local users to bypass the TXT protection mechanism through unspecified vectors when the Measured Launch Environment (MLE) is invoked. Affected systems include specific Intel chipset generations (QM77, QS77, Q77, C216, Q67, C202, C204, C206, QM67, QS67) running SINIT ACM versions before 1.2.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your Intel chipset modelRun 'dmidecode -t baseboard' or check system documentation to identify the exact chipset (e.g., C202, C204, C206, C216, QM67, QS67, Q67, QM77, QS77, Q77)Affected if The chipset model matches one of the affected chipsets listed in the CVE (C202, C204, C206, C216, QM67, QS67, Q67, QM77, QS77, Q77, C204, C206)
-
Check if Intel TXT is enabledUse Intel TXT compatibility checker tool (txt-checker or similar), or check BIOS/UEFI settings for 'Intel Trusted Execution Technology' or 'TXT' feature statusAffected if Intel TXT is currently enabled or operational on the system
-
Determine the SINIT ACM versionRun Intel TXT-specific tooling such as 'txt-stat' (from tboot package), Intel TXT要素 diagnosis tool, or check BIOS/firmware version information that includes SINIT ACM versionAffected if The SINIT ACM version is found to be earlier than version 1.2 (e.g., 1.0, 1.1, or unspecified/unknown)
You are affected if your system uses one of the listed Intel chipsets, has Intel TXT enabled, and the SINIT ACM version is below 1.2
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Intel TXT SINIT ACM update (version 1.2 or later) by updating the system BIOS/firmware to a version containing the patched ACM. Verify TXT functionality remains operational after the update.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-5740 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data