# CVE-2020-8708: Auth bypass in Intel(R) Server Boards, Server Systems and Compute Modules Advisory

> Unauthenticated attackers with adjacent access can escalate privileges on Intel Server Boards and Systems due to improper authentication.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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:** 13 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-32jj-82v4-hh23

## What is CVE-2020-8708?

CVE-2020-8708 is a high-severity authentication bypass vulnerability in Intel(R) Server Boards, Server Systems and Compute Modules Advisory, published on 13 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper authentication for some Intel(R) Server Boards, Server Systems and Compute Modules before version 1.59 may allow an unauthenticated user to potentially enable escalation of privilege via adjacent access.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2020-8708?

It affects 18 products.


Products: Intel Compute Module Hns2600bp Firmware, Intel Compute Module Hns2600kp Firmware, Intel Compute Module Hns2600tp Firmware, Intel Compute Module S2600tp Firmware, Intel Server Board S1200sp Firmware, Intel Server Board S2600bp Firmware, Intel Server Board S2600cw, Intel Server Board S2600kp Firmware, Intel Server Board S2600st Firmware, Intel Server Board S2600wf Firmware, Intel Server Board S2600wt Firmware, Intel Server System Lr1304sp Firmware, Intel Server System Lsvrp Firmware, Intel Server System R1000sp Firmware, Intel Server System R1000wf Firmware, Intel Server System R1000wt Firmware, Intel Server System R2000wf Firmware, Intel Server System R2000wt Firmware.

## How do I fix CVE-2020-8708?

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

## Is CVE-2020-8708 being exploited?

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

## Other vulnerabilities in Intel(R) Server Boards, Server Systems and Compute Modules Advisory

- [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-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)
- [CVE-2020-8718](https://insights.sbomify.com/CVE-2020-8718/): Memory corruption 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-2020-8708 and fix it if it is affected.

What it is: CVE-2020-8708 is a high-severity authentication bypass vulnerability in Intel(R) Server Boards, Server Systems and Compute Modules Advisory, published on 13 Aug 2020. 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-2020-8708 in the wild and no public exploit code.

Affected product: Intel(R) Server Boards, Server Systems and Compute Modules Advisory. 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-2020-8708/ (Markdown: https://insights.sbomify.com/CVE-2020-8708/index.md)
```

## Sources

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

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