dbcve.org
Digsi 5 Engineering SoftwareApplication · Siemens

CVE-2019-10930

HIGH · 7.5 CVSS v3.0 Published 2019-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules (All versions ), DIGSI 5 engineering software (All versions < V7.90), SIPROTEC 5 device types 6MD85, 6MD86, 6MD89, 7UM85, 7SA87, 7SD87, 7SL87, 7VK87, 7SA82, 7SA86, 7SD82, 7SD86, 7SL82, 7SL86, 7SJ86, 7SK82, 7SK85, 7SJ82, 7SJ85, 7UT82, 7UT85, 7UT86, 7UT87 and 7VE85 with CPU variants CP300 and CP100 and the respective Ethernet communication modules (All versions < V7.90), SIPROTEC 5 device types 7SS85 and 7KE85 (All versions < V8.01), SIPROTEC 5 device types with CPU variants CP200 and the respective Ethernet communication modules (All versions). A remote attacker could use specially crafted packets sent to port 443/TCP to upload, download or delete files in certain parts of the file system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability in Siemens SIPROTEC 5 devices and DIGSI 5 engineering software allows remote attackers to upload, download, or delete files in restricted filesystem locations via specially crafted HTTP packets sent to port 443/TCP.

MitigationUpgrade SIPROTEC 5 firmware to V7.90 or later (or V8.01 for 7SS85/7KE85 models) and DIGSI 5 to V7.90 or later. Additionally, restrict network access to port 443/TCP using firewalls or VLANs to limit exposure to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Digsi 5 Engineering SoftwareApplication
Affected:= 7.90
Siprotec 5 Digsi Device DriverApplication
Affected:= 7.90

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DIGSI 5 Engineering Software installation
    Check installed programs on Windows systems for 'Siemens DIGSI 5' or 'DIGSI 5' in the program list, then check the software version through Windows Programs and Features or the application's About/Help menu
    Affected if DIGSI 5 version 7.90 is installed
  2. Identify SIPROTEC 5 device firmware version
    Access the SIPROTEC 5 device web interface or management console, or query the device via its management protocol to retrieve the firmware version
    Affected if SIPROTEC 5 device firmware version is 7.90
  3. Check port 443/TCP exposure
    Perform a network port scan against the SIPROTEC 5 device IP address on TCP port 443, or review firewall rules and network segmentation policies to determine if port 443 is accessible from untrusted networks
    Affected if Port 443/TCP on the SIPROTEC 5 device is reachable from untrusted or external network segments
  4. Verify HTTP service availability on device
    Send an HTTP request to the SIPROTEC 5 device on port 443 (https) and confirm the web service responds, indicating the vulnerable HTTP interface is enabled
    Affected if The device HTTP/HTTPS web service on port 443 is active and responding

You are affected if either DIGSI 5 version 7.90 or SIPROTEC 5 firmware version 7.90 is in use AND port 443/TCP is network-accessible to untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SIPROTEC 5 firmware to V7.90 or later (or V8.01 for 7SS85/7KE85 models) and DIGSI 5 to V7.90 or later. Additionally, restrict network access to port 443/TCP using firewalls or VLANs to limit exposure to untrusted networks.

Fix this in Digsi 5 Engineering Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10930 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data