# CVE-2018-12169: Auth bypass in n/a

> A logic error in Intel Core processor firmware allows a physical attacker to bypass firmware authentication mechanisms.

- **Severity:** High 7.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7hjg-jw54-wcj9

## What is CVE-2018-12169?

CVE-2018-12169 is a high-severity authentication bypass vulnerability in n/a, published on 21 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Platform sample code firmware in 4th Generation Intel Core Processor, 5th Generation Intel Core Processor, 6th Generation Intel Core Processor, 7th Generation Intel Core Processor and 8th Generation Intel Core Processor contains a logic error which may allow physical attacker to potentially bypass firmware authentication.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-12169?

It affects 32 products.


Products: Intel Core I3, Intel Core I5, Intel Core I7, Intel Core I9, Lenovo Thinkpad 11e, Lenovo Thinkpad E480, Lenovo Thinkpad E580, Lenovo Thinkpad L380, Lenovo Thinkpad L380 Yoga, Lenovo Thinkpad L480, Lenovo Thinkpad L580, Lenovo Thinkpad P51, Lenovo Thinkpad P51s, Lenovo Thinkpad P52, Lenovo Thinkpad P52s, Lenovo Thinkpad P71, Lenovo Thinkpad P72, Lenovo Thinkpad T25, Lenovo Thinkpad T470, Lenovo Thinkpad T470p and 12 more.

## How do I fix CVE-2018-12169?

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

## Is CVE-2018-12169 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-3615](https://insights.sbomify.com/CVE-2018-3615/): Information disclosure in Multiple (high 7.3)
- [CVE-2017-5704](https://insights.sbomify.com/CVE-2017-5704/): Information disclosure in Intel Core Processor (medium 6.7)
- [CVE-2018-3620](https://insights.sbomify.com/CVE-2018-3620/): Information disclosure in Multiple (medium 5.6)
- [CVE-2018-3646](https://insights.sbomify.com/CVE-2018-3646/): Information disclosure in Multiple (medium 5.6)
- [CVE-2018-3619](https://insights.sbomify.com/CVE-2018-3619/): Information disclosure in Intel Optane memory (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12169 and fix it if it is affected.

What it is: CVE-2018-12169 is a high-severity authentication bypass vulnerability in n/a, published on 21 Sep 2018. 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-2018-12169 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-2018-12169/ (Markdown: https://insights.sbomify.com/CVE-2018-12169/index.md)
```

## Sources

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

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