# CVE-2018-12173: Missing authorization in Intel Server Boards Firmware

> Unauthenticated local attackers can execute arbitrary code, disclose information, escalate privileges, or cause denial of service due to insufficient firmware access protection.

- **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:** 10 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x4rx-5q6p-5972

## What is CVE-2018-12173?

CVE-2018-12173 is a high-severity missing authorization vulnerability in Intel Server Boards Firmware, published on 10 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient access protection in firmware in Intel Server Board, Intel Server System and Intel Compute Module before firmware version 00.01.0014 may allow an unauthenticated attacker to potentially execute arbitrary code resulting in information disclosure, escalation of privilege and/or denial of service via local access.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 14 products.


Products: Intel Compute Module Hns2600bp Firmware, Intel Compute Module Hns2600bpr Firmware, Intel Server Board S2600bp Firmware, Intel Server Board S2600bpr Firmware, Intel Server Board S2600st Firmware, Intel Server Board S2600str Firmware, Intel Server Board S2600wf Firmware, Intel Server Board S2600wfr Firmware, Intel Server System H2000g Firmware, Intel Server System H2000gr Firmware, Intel Server System R1000wf Firmware, Intel Server System R1000wfr Firmware, Intel Server System R2000wf Firmware, Intel Server System R2000wfr Firmware.

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

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

## Is CVE-2018-12173 being exploited?

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

## Other vulnerabilities in Intel Server Boards Firmware

- [CVE-2020-8706](https://insights.sbomify.com/CVE-2020-8706/): Memory corruption in Intel(R) Server Boards, Server Systems and Compute Modules Advisory (high 8.8)
- [CVE-2020-8707](https://insights.sbomify.com/CVE-2020-8707/): Memory corruption in Intel(R) Server Boards, Server Systems and Compute Modules Advisory (high 8.8)
- [CVE-2020-8708](https://insights.sbomify.com/CVE-2020-8708/): Auth bypass in Intel(R) Server Boards, Server Systems and Compute Modules Advisory (high 8.8)
- [CVE-2020-8709](https://insights.sbomify.com/CVE-2020-8709/): Auth bypass in Intel(R) Server Boards, Server Systems and Compute Modules Advisory (high 8.8)
- [CVE-2020-8713](https://insights.sbomify.com/CVE-2020-8713/): Auth bypass in Intel(R) Server Boards, Server Systems and Compute Modules Advisory (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12173 is a high-severity missing authorization vulnerability in Intel Server Boards Firmware, published on 10 Oct 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-12173 in the wild and no public exploit code.

Affected product: Intel Server Boards Firmware. 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-12173/ (Markdown: https://insights.sbomify.com/CVE-2018-12173/index.md)
```

## Sources

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

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