# CVE-2020-12493: Critical Vulnerability in SWARCO CPU LS4000

> An open debugging port allows remote attackers to gain root access and disrupt operations on SWARCO CPU LS4000 devices.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2fp8-2m27-8mrc

## What is CVE-2020-12493?

CVE-2020-12493 is a critical authentication bypass vulnerability in SWARCO CPU LS4000, published on 29 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An open port used for debugging in SWARCOs CPU LS4000 Series with versions starting with G4... grants root access to the device without access control via network. A malicious user could use this vulnerability to get access to the device and disturb operations with connected devices.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Swarco Cpu Ls4000 Firmware.

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

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

## Is CVE-2020-12493 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12493 is a critical authentication bypass vulnerability in SWARCO CPU LS4000, published on 29 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12493 in the wild and no public exploit code.

Affected product: SWARCO CPU LS4000. 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-12493/ (Markdown: https://insights.sbomify.com/CVE-2020-12493/index.md)
```

## Sources

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

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