dbcve.org
Siprotec 5 6md85 FirmwareOperating system · Siemens

CVE-2022-45044

MEDIUM · 5.3 CVSS v3.1 Published 2022-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 6MD84 (CP300) (All versions < V9.50), SIPROTEC 5 6MD85 (CP200) (All versions), SIPROTEC 5 6MD85 (CP300) (All versions < V9.50), SIPROTEC 5 6MD86 (CP200) (All versions), SIPROTEC 5 6MD86 (CP300) (All versions < V9.50), SIPROTEC 5 6MD89 (CP300) (All versions < V9.64), SIPROTEC 5 6MU85 (CP300) (All versions < V9.50), SIPROTEC 5 7KE85 (CP200) (All versions), SIPROTEC 5 7KE85 (CP300) (All versions < V9.64), SIPROTEC 5 7SA82 (CP100) (All versions < V8.90), SIPROTEC 5 7SA82 (CP150) (All versions < V9.50), SIPROTEC 5 7SA84 (CP200) (All versions), SIPROTEC 5 7SA86 (CP200) (All versions), SIPROTEC 5 7SA86 (CP300) (All versions < V9.50), SIPROTEC 5 7SA87 (CP200) (All versions), SIPROTEC 5 7SA87 (CP300) (All versions < V9.50), SIPROTEC 5 7SD82 (CP100) (All versions < V8.90), SIPROTEC 5 7SD82 (CP150) (All versions < V9.50), SIPROTEC 5 7SD84 (CP200) (All versions), SIPROTEC 5 7SD86 (CP200) (All versions), SIPROTEC 5 7SD86 (CP300) (All versions < V9.50), SIPROTEC 5 7SD87 (CP200) (All versions), SIPROTEC 5 7SD87 (CP300) (All versions < V9.50), SIPROTEC 5 7SJ81 (CP100) (All versions < V8.89), SIPROTEC 5 7SJ81 (CP150) (All versions < V9.50), SIPROTEC 5 7SJ82 (CP100) (All versions < V8.89), SIPROTEC 5 7SJ82 (CP150) (All versions < V9.50), SIPROTEC 5 7SJ85 (CP200) (All versions), SIPROTEC 5 7SJ85 (CP300) (All versions < V9.50), SIPROTEC 5 7SJ86 (CP200) (All versions), SIPROTEC 5 7SJ86 (CP300) (All versions < V9.50), SIPROTEC 5 7SK82 (CP100) (All versions < V8.89), SIPROTEC 5 7SK82 (CP150) (All versions < V9.50), SIPROTEC 5 7SK85 (CP200) (All versions), SIPROTEC 5 7SK85 (CP300) (All versions < V9.50), SIPROTEC 5 7SL82 (CP100) (All versions < V8.90), SIPROTEC 5 7SL82 (CP150) (All versions < V9.50), SIPROTEC 5 7SL86 (CP200) (All versions), SIPROTEC 5 7SL86 (CP300) (All versions < V9.50), SIPROTEC 5 7SL87 (CP200) (All versions), SIPROTEC 5 7SL87 (CP300) (All versions < V9.50), SIPROTEC 5 7SS85 (CP200) (All versions), SIPROTEC 5 7SS85 (CP300) (All versions < V9.50), SIPROTEC 5 7ST85 (CP200) (All versions), SIPROTEC 5 7ST85 (CP300) (All versions < V9.64), SIPROTEC 5 7ST86 (CP300) (All versions < V9.64), SIPROTEC 5 7SX82 (CP150) (All versions < V9.50), SIPROTEC 5 7SX85 (CP300) (All versions < V9.50), SIPROTEC 5 7UM85 (CP300) (All versions < V9.50), SIPROTEC 5 7UT82 (CP100) (All versions < V8.90), SIPROTEC 5 7UT82 (CP150) (All versions < V9.50), SIPROTEC 5 7UT85 (CP200) (All versions), SIPROTEC 5 7UT85 (CP300) (All versions < V9.50), SIPROTEC 5 7UT86 (CP200) (All versions), SIPROTEC 5 7UT86 (CP300) (All versions < V9.50), SIPROTEC 5 7UT87 (CP200) (All versions), SIPROTEC 5 7UT87 (CP300) (All versions < V9.50), SIPROTEC 5 7VE85 (CP300) (All versions < V9.50), SIPROTEC 5 7VK87 (CP200) (All versions), SIPROTEC 5 7VK87 (CP300) (All versions < V9.50), SIPROTEC 5 7VU85 (CP300) (All versions < V9.50), SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1) (All versions installed on CP200 devices), SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1) (All versions < V9.50 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 installed on CP200 devices), SIPROTEC 5 Communication Module ETH-BB-2FO (Rev. 1) (All versions < V9.50 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.50), SIPROTEC 5 Compact 7SX800 (CP050) (All versions < V9.50). Affected devices do not properly restrict secure client-initiated renegotiations within the SSL and TLS protocols. This could allow an attacker to create a denial of service condition on the ports 443/tcp and 4443/tcp for the duration of the attack.

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 SSL/TLS implementation of affected SIPROTEC 5 devices, which do not properly restrict client-initiated renegotiations. An attacker can exploit this by sending repeated renegotiation requests to ports 443/tcp and 4443/tcp, causing resource exhaustion and resulting in a denial of service condition.

MitigationUpdate affected devices to the vendor-specified fixed firmware versions (V9.50, V9.64, V8.90, or V8.89 depending on device model and CP type). If updates cannot be applied immediately, consider blocking or rate-limiting external access to ports 443/tcp and 4443/tcp.

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

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
Low

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

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
    Access the device web interface or use the device management console to confirm the exact model number (6md85, 6md86, 6md89, 6mu85, 7ke85, 7sa82, 7sa86, or 7sa87)
    Affected if The device model matches any of the listed affected models
  2. Check the installed firmware version
    Access the device management interface or use the device command line to retrieve the current firmware version
    Affected if The firmware version is any version prior to the vendor fixed versions (V9.50, V9.64, V8.90, or V8.89 depending on device model and CP type)
  3. Verify if ports 443/tcp and 4443/tcp are exposed
    Perform a network port scan from an external or internal system to check if ports 443/tcp and 4443/tcp are listening and accessible
    Affected if Either port 443/tcp or 4443/tcp is open and accessible to untrusted networks
  4. Confirm SSL/TLS renegotiation is enabled
    Use an SSL/TLS scanning tool (such as testssl.sh or OpenSSL s_client) to connect to ports 443/tcp and 4443/tcp and verify if secure renegotiation is supported
    Affected if The SSL/TLS handshake response indicates that client-initiated renegotiation is allowed

The device is affected if it is one of the listed SIPROTEC 5 models with firmware versions prior to the fixed releases AND ports 443/tcp or 4443/tcp are accessible with SSL/TLS renegotiation enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected devices to the vendor-specified fixed firmware versions (V9.50, V9.64, V8.90, or V8.89 depending on device model and CP type). If updates cannot be applied immediately, consider blocking or rate-limiting external access to ports 443/tcp and 4443/tcp.

Recommended fix High confidence

V9.50, V9.64, V8.90, or V8.89 (depending on specific device model and CP version - see steps for details)

  1. 1. Identify the specific SIPROTEC 5 device model (e.g., 6md85, 7sa82) and CP version (CP100, CP150, CP200, CP300) in use
  2. 2. Determine the current firmware version installed on the affected device
  3. 3. Consult Siemens product documentation or the Siemens Industry Online Support portal to obtain the appropriate firmware update
  4. 4. For CP300 devices of 6md85, 6md86, 7sa86, 7sa87, 7sd86, 7sd87, 7sj85, 7sj86, 7sk85, 7sl86, 7sl87, 7ss85, 7ut85, 7ut86, 7ut87, 7ve85, 7vk87, 7vu85: upgrade to firmware version V9.50 or later
  5. 5. For CP300 devices of 6md89, 7ke85, 7st85, 7st86: upgrade to firmware version V9.64 or later
  6. 6. For CP100 devices of 7sa82, 7sd82, 7sl82, 7ut82: upgrade to firmware version V8.90 or later
  7. 7. For CP100 devices of 7sj81, 7sj82, 7sk82: upgrade to firmware version V8.89 or later
  8. 8. For CP150 devices of 7sa82, 7sd82, 7sl82, 7ut82, 7sx82: upgrade to firmware version V9.50 or later
Caveat Standard firmware updates typically maintain configuration compatibility, but always backup configuration before upgrading and test in a non-production environment first

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

Fix this in Siprotec 5 6md85 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45044 — 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-2022-45044 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