dbcve.org
6ed1052 1md08 0ba1 FirmwareOperating system · Siemens

CVE-2022-42784

MEDIUM · 6.8 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to after 8.3 or later.
See remediation →
73/100
Remediation priority · Elevated
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 LOGO! 12/24RCE (6ED1052-1MD08-0BA1) (All versions >= V8.3), LOGO! 12/24RCEo (6ED1052-2MD08-0BA1) (All versions >= V8.3), LOGO! 230RCE (6ED1052-1FB08-0BA1) (All versions >= V8.3), LOGO! 230RCEo (6ED1052-2FB08-0BA1) (All versions >= V8.3), LOGO! 24CE (6ED1052-1CC08-0BA1) (All versions >= V8.3), LOGO! 24CEo (6ED1052-2CC08-0BA1) (All versions >= V8.3), LOGO! 24RCE (6ED1052-1HB08-0BA1) (All versions >= V8.3), LOGO! 24RCEo (6ED1052-2HB08-0BA1) (All versions >= V8.3), SIPLUS LOGO! 12/24RCE (6AG1052-1MD08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 12/24RCEo (6AG1052-2MD08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 230RCE (6AG1052-1FB08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 230RCEo (6AG1052-2FB08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24CE (6AG1052-1CC08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24CEo (6AG1052-2CC08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24RCE (6AG1052-1HB08-7BA1) (All versions >= V8.3), SIPLUS LOGO! 24RCEo (6AG1052-2HB08-7BA1) (All versions >= V8.3). Affected devices are vulnerable to an electromagnetic fault injection. This could allow an attacker to dump and debug the firmware, including the manipulation of memory. Further actions could allow to inject public keys of custom created key pairs which are then signed by the product CA. The generation of a custom certificate allows communication with, and impersonation of, any device of the same version.

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

This vulnerability in Siemens LOGO! devices (versions >= V8.3) allows electromagnetic fault injection attacks that can dump and debug firmware, manipulate memory, inject custom public keys that get signed by the product CA, and generate certificates for impersonating any device of the same version. The attack enables full device impersonation and cryptographic bypass.

MitigationImplement physical access controls to prevent unauthorized physical access to devices; network isolate LOGO! devices; monitor for anomalous device behavior; consult Siemens for available firmware hardening or hardware countermeasures.

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
6ed1052 1md08 0ba1 FirmwareOperating system
Affected:<= 8.3
6ed1052 2md08 0ba1 FirmwareOperating system
Affected:<= 8.3
6ed1052 1cc08 0ba1 FirmwareOperating system
Affected:<= 8.3
6ed1052 2cc08 0ba1 FirmwareOperating system
Affected:<= 8.3
6ed1052 1hb08 0ba1 FirmwareOperating system
Affected:<= 8.3
6ed1052 2hb08 0ba1 FirmwareOperating system
Affected:<= 8.3
6ed1052 1fb08 0ba1 FirmwareOperating system
Affected:<= 8.3
6ed1052 2fb08 0ba1 FirmwareOperating system
Affected:<= 8.3

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Siemens LOGO! device model
    Locate the device nameplate or check procurement records for the exact part number. Look for the 6ed1052-xxxx-xxxx numbering scheme.
    Affected if The part number matches any of: 6ed1052 1md08 0ba1, 6ed1052 2md08 0ba1, 6ed1052 1cc08 0ba1, 6ed1052 2cc08 0ba1, 6ed1052 1hb08 0ba1, 6ed1052 2hb08 0ba1, 6ed1052 1fb08 0ba1, or 6ed1052 2fb08 0ba1.
  2. Check installed firmware version
    Access the LOGO! device web interface or use the LOGO! Comfort software to query the device firmware version. The version is typically displayed in the device information or system properties.
    Affected if The firmware version is 8.3 or lower (e.g., 8.2, 8.1, 8.0).
  3. Verify device is accessible physically
    Conduct a physical security assessment of the environment where the LOGO! device is deployed. Check for unlocked cabinets, exposed ports, or lack of tamper evidence.
    Affected if The device is located in an area with unrestricted physical access or without physical tamper protections.
  4. Inspect for unexpected certificates or keys
    If administrative access is available, review the device certificate store or PKI configuration for any unrecognized public keys or certificates that were not provisioned by your organization.
    Affected if Unexpected certificates or public keys are present that do not match your organization's PKI infrastructure.

You are affected if you have a Siemens LOGO! device with a matching part number running firmware version 8.3 or lower, and the device or its network is accessible to an attacker who could perform physical fault injection.

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 a release after 8.3
Interim mitigation

Implement physical access controls to prevent unauthorized physical access to devices; network isolate LOGO! devices; monitor for anomalous device behavior; consult Siemens for available firmware hardening or hardware countermeasures.

Recommended fix Moderate confidence
  1. This is a hardware-level vulnerability (electromagnetic fault injection) that cannot be fixed via software upgrade, patch, or configuration changes.
  2. Implement physical security controls to limit unauthorized access to the device.
  3. Place the affected devices in secure locations with restricted physical access.
  4. Monitor for signs of tampering with the device hardware.
  5. Consider replacing vulnerable devices with newer models if available that include hardware-level fault injection protections.
  6. Refer to Siemens security guidelines for industrial automation devices for additional protective measures.

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

Fix this in 6ed1052 1md08 0ba1 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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