Siprotec 5 6md85 FirmwareOperating system · Siemens

CVE-2023-28766

HIGH · 7.5 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 9.40 or later.
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 SIPROTEC 5 6MD85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 6MD86 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 6MD89 (CP300) (All versions >= V7.80 < V9.64), SIPROTEC 5 6MU85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7KE85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SA82 (CP100) (All versions < V8.90), SIPROTEC 5 7SA82 (CP150) (All versions < V9.40), SIPROTEC 5 7SA86 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SA87 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SD82 (CP100) (All versions < V8.90), SIPROTEC 5 7SD82 (CP150) (All versions < V9.40), SIPROTEC 5 7SD86 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SD87 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SJ81 (CP100) (All versions < V8.89), SIPROTEC 5 7SJ81 (CP150) (All versions < V9.40), SIPROTEC 5 7SJ82 (CP100) (All versions < V8.89), SIPROTEC 5 7SJ82 (CP150) (All versions < V9.40), SIPROTEC 5 7SJ85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SJ86 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SK82 (CP100) (All versions < V8.89), SIPROTEC 5 7SK82 (CP150) (All versions < V9.40), SIPROTEC 5 7SK85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SL82 (CP100) (All versions < V8.90), SIPROTEC 5 7SL82 (CP150) (All versions < V9.40), SIPROTEC 5 7SL86 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SL87 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SS85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7ST85 (CP300) (All versions >= V7.80 < V9.64), SIPROTEC 5 7ST86 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7SX82 (CP150) (All versions < V9.40), SIPROTEC 5 7SX85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7UM85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7UT82 (CP100) (All versions < V8.90), SIPROTEC 5 7UT82 (CP150) (All versions < V9.40), SIPROTEC 5 7UT85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7UT86 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7UT87 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7VE85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7VK87 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 7VU85 (CP300) (All versions >= V7.80 < V9.40), SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1) (All versions < V9.40 installed on CP150 and CP300 devices), SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1) (All versions < V8.89 installed on CP100 devices), SIPROTEC 5 Communication Module ETH-BB-2FO (Rev. 1) (All versions < V9.40 installed on CP150 and CP300 devices), SIPROTEC 5 Communication Module ETH-BB-2FO (Rev. 1) (All versions < V8.89 installed on CP100 devices), SIPROTEC 5 Communication Module ETH-BD-2FO (All versions < V9.40), SIPROTEC 5 Compact 7SX800 (CP050) (All versions < V9.40). Affected devices lack proper validation of http request parameters of the hosted web service. An unauthenticated remote attacker could send specially crafted packets that could cause denial of service condition of the target device.

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

The vulnerability exists in the web service component of SIPROTEC 5 devices (multiple protection relay models). Affected devices fail to properly validate HTTP request parameters, allowing unauthenticated remote attackers to send specially crafted HTTP packets that cause a denial of service condition.

MitigationUpgrade affected SIPROTEC 5 devices to the patched versions (V9.40, V8.90, or V8.89 depending on device type and CP platform) as specified in the Siemens advisory. For devices that cannot be immediately updated, consider network segmentation to limit exposure to the web service interface.

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
Siprotec 5 6md85 FirmwareOperating system
Affected:all versions< 9.40
Siprotec 5 6md86 FirmwareOperating system
Affected:all versions< 9.40
Siprotec 5 6md89 FirmwareOperating system
Affected:all versions
Siprotec 5 6mu85 FirmwareOperating system
Affected:< 9.40
Siprotec 5 7ke85 FirmwareOperating system
Affected:all versions< 9.40
Siprotec 5 7sa82 FirmwareOperating system
Affected:all versions< 9.40
Siprotec 5 7sa86 FirmwareOperating system
Affected:all versions< 9.40
Siprotec 5 7sa87 FirmwareOperating system
Affected:all versions< 9.40

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
None
Availability
High

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

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 the SIPROTEC 5 device model
    Locate the device model number on the physical device or in the device management interface. Common models include 6md85, 6md86, 6md89, 6mu85, 7ke85, 7sa82, 7sa86, and 7sa87.
    Affected if The device model matches one of the affected models listed in the CVE advisory.
  2. Determine the installed firmware version
    Access the device web interface or management console and locate the firmware version information. This is typically found under System, Device Info, or About sections.
    Affected if The firmware version is below 9.40 (or below 8.90/8.89 for specific models as noted in the Siemens advisory). For 6md89, all versions are affected.
  3. Verify if the web service component is enabled
    Check the device configuration for HTTP/HTTPS web service settings. This is usually found in the device network configuration or communication settings menu.
    Affected if The web service HTTP interface is enabled and accessible on the network.
  4. Assess network accessibility of the web interface
    Determine if the device web interface is reachable from network segments outside the protected OT environment. Use network scanning or review firewall rules.
    Affected if The web service is exposed to untrusted network segments or the internet.

A user is affected if their SIPROTEC 5 device model and firmware version fall within the affected ranges AND the web service component is enabled and accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 9.40 or later
Fixed in 9.40
Interim mitigation

Upgrade affected SIPROTEC 5 devices to the patched versions (V9.40, V8.90, or V8.89 depending on device type and CP platform) as specified in the Siemens advisory. For devices that cannot be immediately updated, consider network segmentation to limit exposure to the web service interface.

Recommended fix High confidence

Firmware version 9.40 or higher (9.64 for 6MD89 and 7ST85 models)

  1. Identify the specific Siprotec 5 device model and CP type (CP100, CP150, or CP300) from the affected product list
  2. Determine the current firmware version installed on the device
  3. For CP300 devices (6MD85, 6MD86, 6MD89, 6MU85, 7KE85, 7SA86, 7SA87, etc.): upgrade firmware to version 9.40 or higher (9.64 for 6MD89 and 7ST85)
  4. For CP150 devices: upgrade firmware to version 9.40 or higher
  5. For CP100 devices (7SA82, 7SD82, 7SL82, 7UT82): upgrade firmware to version 8.90 or higher
  6. For CP050 devices (Compact 7SX800): upgrade firmware to version 9.40 or higher
  7. For communication modules ETH-BA-2EL, ETH-BB-2FO, ETH-BD-2FO: upgrade to version 9.40 (or 8.89 for CP100 devices)
  8. After upgrade, verify the web service is operational and the vulnerability is remediated
Caveat Standard firmware upgrade risks apply - ensure backup of configuration and follow Siemens upgrade documentation; minor configuration changes may be needed between major version jumps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Siprotec 5 6md85 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2023-28766 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