# CVE-2018-4858: Other in IEC 61850 system configurator, DIGSI 5 (affected as IEC 61850 system configurator is incorporated), DIGSI 4, SICAM PAS/PQS, SICAM PQ Analyzer, SICAM SCC

> Attackers can exfiltrate data or execute code on Siemens IEC 61850 and SICAM products via crafted network requests requiring user interaction.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pq3v-xpfj-jcqv

## What is CVE-2018-4858?

CVE-2018-4858 is a high-severity vulnerability in Siemens AG IEC 61850 system configurator, DIGSI 5 (affected as IEC 61850 system configurator is incorporated), DIGSI 4, SICAM PAS/PQS, SICAM PQ Analyzer, SICAM SCC, published on 9 Jul 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in IEC 61850 system configurator (All versions < V5.80), DIGSI 5 (affected as IEC 61850 system configurator is incorporated) (All versions < V7.80), DIGSI 4 (All versions < V4.93), SICAM PAS/PQS (All versions < V8.11), SICAM PQ Analyzer (All versions < V3.11), SICAM SCC (All versions < V9.02 HF3). A service of the affected products listening on all of the host's network interfaces on either port 4884/TCP, 5885/TCP, or port 5886/TCP could allow an attacker to either exfiltrate limited data from the system or to execute code with Microsoft Windows user permissions. Successful exploitation requires an attacker to be able to send a specially crafted network request to the vulnerable service and a user interacting with the service's client application on the host. In order to execute arbitrary code with Microsoft Windows user permissions, an attacker must be able to plant the code in advance on the host by other means. The vulnerability has limited impact to confidentiality and integrity of the affected system. At the time of advisory publication no public exploitation of this security vulnerability was known. Siemens confirms the security vulnerability and provides mitigations to resolve the security issue.

Weakness: CWE-284 (Improper Access Control)

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

It affects 6 products.


Products: Siemens Digsi 4 Firmware, Siemens Digsi 5 Firmware, Siemens Ec 61850 System Configurator Firmware, Siemens Sicam Pas\/Pqs, Siemens Sicam Pq Analyzer Firmware, Siemens Sicam Scc Firmware.

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

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

## Is CVE-2018-4858 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-4858 is a high-severity vulnerability in Siemens AG IEC 61850 system configurator, DIGSI 5 (affected as IEC 61850 system configurator is incorporated), DIGSI 4, SICAM PAS/PQS, SICAM PQ Analyzer, SICAM SCC, published on 9 Jul 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-4858 in the wild and no public exploit code.

Affected product: Siemens AG IEC 61850 system configurator, DIGSI 5 (affected as IEC 61850 system configurator is incorporated), DIGSI 4, SICAM PAS/PQS, SICAM PQ Analyzer, SICAM SCC. 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-4858/ (Markdown: https://insights.sbomify.com/CVE-2018-4858/index.md)
```

## Sources

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

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