# CVE-2018-13804: Auth bypass in SIMATIC IT LMS, SIMATIC IT Production Suite, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing

> An attacker with network access and a valid username can bypass application-level authentication in Siemens SIMATIC IT systems, compromising confidentiality, integrity, and availability.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/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:** 13 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hf5v-q9xg-wmjx

## What is CVE-2018-13804?

CVE-2018-13804 is a high-severity authentication bypass vulnerability in Siemens AG SIMATIC IT LMS, SIMATIC IT Production Suite, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, published on 13 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in SIMATIC IT LMS (All versions), SIMATIC IT Production Suite (Versions V7.1 < V7.1 Upd3), SIMATIC IT UA Discrete Manufacturing (Versions < V1.2), SIMATIC IT UA Discrete Manufacturing (Versions V1.2), SIMATIC IT UA Discrete Manufacturing (Versions V1.3), SIMATIC IT UA Discrete Manufacturing (Versions V2.3), SIMATIC IT UA Discrete Manufacturing (Versions V2.4). An attacker with network access to the installation could bypass the application-level authentication. In order to exploit the vulnerability, an attacker must obtain network access to an affected installation and must obtain a valid username to the system. Successful exploitation requires no user privileges and no user interaction. The vulnerability could allow an attacker to compromise confidentiality, integrity and availability of the system. At the time of advisory publication no public exploitation of this vulnerability was known.

Weakness: CWE-287 (Improper Authentication)

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

It affects 3 products.


Products: Siemens Simatic It Line Monitoring System, Siemens Simatic It Production Suite, Siemens Simatic It Ua Discrete Manufacturing.

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

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

## Is CVE-2018-13804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-13804 is a high-severity authentication bypass vulnerability in Siemens AG SIMATIC IT LMS, SIMATIC IT Production Suite, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, published on 13 Dec 2018. 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-2018-13804 in the wild and no public exploit code.

Affected product: Siemens AG SIMATIC IT LMS, SIMATIC IT Production Suite, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing, SIMATIC IT UA Discrete Manufacturing. 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-13804/ (Markdown: https://insights.sbomify.com/CVE-2018-13804/index.md)
```

## Sources

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

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