dbcve.org
6es7412 2ek07 0ab0 FirmwareOperating system · Siemens

CVE-2022-47374

HIGH · 7.5 CVSS v3.1 Published 2023-12-12
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 SIMATIC PC-Station Plus (All versions), SIMATIC S7-400 CPU 412-2 PN V7 (All versions), SIMATIC S7-400 CPU 414-3 PN/DP V7 (All versions), SIMATIC S7-400 CPU 414F-3 PN/DP V7 (All versions), SIMATIC S7-400 CPU 416-3 PN/DP V7 (All versions), SIMATIC S7-400 CPU 416F-3 PN/DP V7 (All versions), SINAMICS S120 (incl. SIPLUS variants) (All versions < V5.2 SP3 HF15), SIPLUS S7-400 CPU 414-3 PN/DP V7 (All versions), SIPLUS S7-400 CPU 416-3 PN/DP V7 (All versions). The affected products do not handle HTTP(S) requests to the web server correctly. This could allow an attacker to exhaust system resources and create a denial of service condition for the 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 stems from improper HTTP(S) request handling in the web servers of affected SIMATIC and SINAMICS devices. Attackers can send specially crafted requests that exhaust system resources, leading to denial of service.

MitigationApply available vendor patches (SINAMICS S120 requires V5.2 SP3 HF15 or later). For unpatched devices, implement network segmentation, restrict web server access via firewall rules, or disable the web server if not operationally required.

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
6es7412 2ek07 0ab0 FirmwareOperating system
Affected:all versions
6es7414 3em07 0ab0 FirmwareOperating system
Affected:all versions
6es7414 3fm07 0ab0 FirmwareOperating system
Affected:all versions
6es7416 3es07 0ab0 FirmwareOperating system
Affected:all versions
6es7416 3fs07 0ab0 FirmwareOperating system
Affected:all versions
6ag1414 3em07 7ab0 FirmwareOperating system
Affected:all versions
6ag1416 3es07 7ab0 FirmwareOperating system
Affected:all versions
Sinamics S120 FirmwareOperating system
Affected:all versions= 4.7= 4.8= 4.9= 5.0= 5.1= 5.2

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 device model
    Locate the device nameplate or check the device configuration to determine if the model is one of: 6es7412 2ek07 0ab0, 6es7414 3em07 0ab0, 6es7414 3fm07 0ab0, 6es7416 3es07 0ab0, 6es7416 3fs07 0ab0, 6ag1414 3em07 7ab0, 6ag1416 3es07 7ab0, or Sinamics S120
    Affected if The device model matches any of the listed affected product numbers
  2. Check if the web server feature is enabled
    Access the device web interface via HTTP/HTTPS on the configured port (typically 80 or 443). If a login page or device status page loads, the web server is enabled
    Affected if The web server is accessible and responds to HTTP/HTTPS requests
  3. Determine the firmware version for SIMATIC devices
    For SIMATIC PLCs (6es7412, 6es7414, 6es7416, 6ag1414, 6ag1416), access the device via TIA Portal, Step 7, or the device web interface to read the firmware version
    Affected if The device is a SIMATIC model and runs any firmware version (all versions are affected)
  4. Determine the firmware version for Sinamics S120
    Access the Sinamics S120 via the web server, STARTER software, or Sinamics Startdrive to read the firmware version
    Affected if The device is a Sinamics S120 and runs firmware version 4.7, 4.8, 4.9, 5.0, 5.1, or 5.2, or any version if all versions are affected per the vendor advisory

You are affected if you have a SIMATIC device (6es7412/6es7414/6es7416/6ag1414/6ag1416) or a Sinamics S120 with the web server enabled, regardless of firmware version.

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

Apply available vendor patches (SINAMICS S120 requires V5.2 SP3 HF15 or later). For unpatched devices, implement network segmentation, restrict web server access via firewall rules, or disable the web server if not operationally required.

Recommended fix Moderate confidence

Sinamics S120: V5.2 SP3 HF15 or later; SIMATIC S7-400 CPUs: Contact Siemens for specific fixed version

  1. Identify the specific model and current firmware version of the affected device
  2. For Sinamics S120 (including SIPLUS variants): Obtain and install firmware version V5.2 SP3 HF15 or later from Siemens
  3. For SIMATIC S7-400 CPU models (412-2 PN, 414-3 PN/DP, 414F-3 PN/DP, 416-3 PN/DP, 416F-3 PN/DP): Contact Siemens customer support to obtain the specific fixed firmware version, as the vulnerability affects all versions
  4. After upgrade, verify the web server functionality and confirm the vulnerability is remediated
  5. Implement network segmentation to limit exposure of the web server interface to trusted networks as an additional mitigation
Caveat Firmware updates may require PLC program revalidation; ensure backups exist before updating

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

Fix this in 6es7412 2ek07 0ab0 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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