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

CVE-2022-47375

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 long file names correctly. This could allow an attacker to create a buffer overflow 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 · moderate confidence

The vulnerability exists in the file name handling routines of affected Siemens SIMATIC and SINAMICS products. Improper validation of file name length allows a buffer overflow when processing excessively long file names, potentially causing device denial of service.

MitigationFor SINAMICS S120, upgrade to version V5.2 SP3 HF15 or later. For other affected products, apply vendor-provided patches or implement network segmentation to limit exposure to untrusted file inputs.

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 SIMATIC PLC model
    Locate the hardware identification label on the PLC module or query the device via TIA Portal, STEP 7, or the device's web interface for the exact product order number (MLFB) such as 6es7412-2ek07-0ab0
    Affected if The product order number matches 6es7412-2ek07-0ab0, 6es7414-3em07-0ab0, 6es7414-3fm07-0ab0, 6es7416-3es07-0ab0, 6es7416-3fs07-0ab0, 6ag1414-3em07-7ab0, or 6ag1416-3es07-7ab0
  2. Identify the SINAMICS S120 model
    Check the drive unit nameplate or query via STARTER, SINAMICS Startdrive, or the device's built-in web server for the product designation
    Affected if The product is a Siemens SINAMICS S120 drive system
  3. Check the firmware version of SIMATIC PLCs
    Connect to the PLC via TIA Portal or STEP 7 and read the firmware version from the device properties, or access via the PLC's web-based management interface
    Affected if The firmware version is any version (all versions of these models are affected)
  4. Check the firmware version of SINAMICS S120
    Query the drive firmware version via STARTER, SINAMICS Startdrive, or the operator panel using the version information screen
    Affected if The firmware version is 4.7, 4.8, 4.9, 5.0, 5.1, 5.2, or any version (the advisory indicates all versions are affected)
  5. Verify if file name handling is accessible
    Determine if the device's file handling routines are exposed to untrusted inputs. This includes assessing whether the device accepts file operations from network sources, removable media, or external memory cards without prior validation
    Affected if The device processes file names from external or network sources without additional input validation layers

You are affected if you have any of the listed SIMATIC PLC models (6es7412/6es7414/6es7416/6ag1414/6ag1416 series) or a SINAMICS S120 drive, regardless of firmware version, and the device's file name handling functionality is accessible to external or untrusted inputs.

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

For SINAMICS S120, upgrade to version V5.2 SP3 HF15 or later. For other affected products, apply vendor-provided patches or implement network segmentation to limit exposure to untrusted file inputs.

Recommended fix High confidence

Sinamics S120: V5.2 SP3 HF15

  1. For Sinamics S120 (incl. SIPLUS variants): Upgrade firmware to version V5.2 SP3 HF15 or later.
  2. For SIMATIC S7-400 CPU models (412-2 PN V7, 414-3 PN/DP V7, 414F-3 PN/DP V7, 416-3 PN/DP V7, 416F-3 PN/DP V7) and SIMATIC PC-Station Plus: No fixed version is currently available per this advisory. Contact Siemens for remediation guidance.
  3. Implement network segmentation and access controls to reduce attack surface until patches are available.
  4. Monitor Siemens CERT portal for updates to this advisory.
Caveat Review Siemens release notes for V5.2 SP3 HF15 for any compatibility considerations before upgrading

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

Fix this in 6es7412 2ek07 0ab0 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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