# CVE-2020-8704: Race condition in a subsystem in the Intel(R) LMS versions before 2039.1.0.0 may allow a privileged user to potentially enable escalation of


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-57c7-hj58-875p

## What is CVE-2020-8704?

CVE-2020-8704 is a medium-severity vulnerability in Intel(R) LMS versions, published on 9 Jun 2021. 

### Official description

Race condition in a subsystem in the Intel(R) LMS versions before 2039.1.0.0 may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 13 products.


Products: Intel Local Manageability Service, Siemens Simatic Field Pg M5 Firmware, Siemens Simatic Field Pg M6 Firmware, Siemens Simatic Ipc427e Firmware, Siemens Simatic Ipc477e Firmware, Siemens Simatic Ipc477e Pro Firmware, Siemens Simatic Ipc527g Firmware, Siemens Simatic Ipc547g Firmware, Siemens Simatic Ipc627e Firmware, Siemens Simatic Ipc647e Firmware, Siemens Simatic Ipc677e Firmware, Siemens Simatic Ipc847e Firmware, Siemens Simatic Itp1000 Firmware.

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

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

## Is CVE-2020-8704 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8704 and fix it if it is affected.

What it is: CVE-2020-8704 is a medium-severity vulnerability in Intel(R) LMS versions, published on 9 Jun 2021. 
Exploitation: There is no known exploitation of CVE-2020-8704 in the wild and no public exploit code.

Affected product: Intel(R) LMS versions. 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-8704/ (Markdown: https://insights.sbomify.com/CVE-2020-8704/index.md)
```

## Sources

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

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