# CVE-2018-4846: Hardcoded credentials in RAPIDLab 1200 systems RAPIDPoint 400 systems RAPIDPoint 500 systems RAPIDLab 1200 Series RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 400 systems

> Attackers can access Siemens lab devices via a hardcoded factory account, compromising confidentiality, integrity, and availability.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vcx8-x3m9-gr6g

## What is CVE-2018-4846?

CVE-2018-4846 is a critical vulnerability in Siemens AG RAPIDLab 1200 systems RAPIDPoint 400 systems RAPIDPoint 500 systems RAPIDLab 1200 Series RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 400 systems, published on 26 Jun 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 RAPIDLab 1200 systems / RAPIDPoint 400 systems / RAPIDPoint 500 systems (All versions_without_ use of Siemens Healthineers Informatics products), RAPIDLab 1200 Series (All versions < V3.3 _with_ Siemens Healthineers Informatics products), RAPIDPoint 500 systems (All versions >= V3.0 _with_ Siemens Healthineers Informatics products), RAPIDPoint 500 systems (V2.4.X_with_ Siemens Healthineers Informatics products), RAPIDPoint 500 systems (All versions =< V2.3 _with_ Siemens Healthineers Informatics products), RAPIDPoint 400 systems (All versions _with_ Siemens Healthineers Informatics products). A factory account with hardcoded password might allow attackers access to the device over port 5900/tcp. Successful exploitation requires no user interaction or privileges and impacts the confidentiality, integrity, and availability of the affected device. At the time of advisory publication, no public exploitation of this security vulnerability is known. Siemens Healthineers confirms the security vulnerability and provides mitigations to resolve the security issue.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 3 products.


Products: Siemens Rapidlab 1200 Firmware, Siemens Rapidpoint 400 Firmware, Siemens Rapidpoint 500 Firmware.

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

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

## Is CVE-2018-4846 being exploited?

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

## Other vulnerabilities in Siemens AG RAPIDLab 1200 systems RAPIDPoint 400 systems RAPIDPoint 500 systems RAPIDLab 1200 Series RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 400 systems

- [CVE-2018-4845](https://insights.sbomify.com/CVE-2018-4845/): Privilege escalation in RAPIDLab 1200 systems / RAPIDPoint 400 systems / RAPIDPoint 500 systems, RAPIDLab 1200 Series, RAPIDPoint 500 systems, RAPIDPoint 500 systems, RAPIDPoint 500 systems, RAPIDPoint 400 systems (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-4846 is a critical vulnerability in Siemens AG RAPIDLab 1200 systems RAPIDPoint 400 systems RAPIDPoint 500 systems RAPIDLab 1200 Series RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 400 systems, published on 26 Jun 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-4846 in the wild and no public exploit code.

Affected product: Siemens AG RAPIDLab 1200 systems RAPIDPoint 400 systems RAPIDPoint 500 systems RAPIDLab 1200 Series RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 500 systems RAPIDPoint 400 systems. 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-4846/ (Markdown: https://insights.sbomify.com/CVE-2018-4846/index.md)
```

## Sources

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

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