CVE-2022-42784

Device impersonation via electromagnetic fault injection

Published Dec 12, 2023 · Updated Oct 8, 2024

Electromagnetic fault injection in Siemens LOGO! and SIPLUS LOGO! V8.3 BM devices allows physically proximate attackers to alter firmware memory. The hardware architecture fails to protect computation from injected electromagnetic faults, enabling firmware extraction and attacker-controlled public keys to be signed by the product CA. Physical access and fault-injection equipment are required; resulting certificates permit communication with and impersonation of any same-version device.

CVSS severity7.6
High
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Electromagnetic fault injection in Siemens LOGO! and SIPLUS LOGO! V8.3 BM devices allows physically proximate attackers to alter firmware memory. The hardware architecture fails to protect computation from injected electromagnetic faults, enabling firmware extraction and attacker-controlled public keys to be signed by the product CA. Physical access and fault-injection equipment are required; resulting certificates permit communication with and impersonation of any same-version device.

The record

CVE
CVE-2022-42784
Published
Dec 12, 2023
Updated
Oct 8, 2024
Vendor
Siemens
Product
SIPLUS LOGO! 24RCEo
Classifications
CWE-1319, T1693
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 12, 2023CVE publishedPublication date reported by the CVE source.
  2. Oct 8, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=V8.3 <*

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Siemens · SIPLUS LOGO! 24RCEoversion=V8.3 <*
Siemens · LOGO! 24CEversion=V8.3 <*
Siemens · SIPLUS LOGO! 24CEversion=V8.3 <*
Siemens · LOGO! 24CEoversion=V8.3 <*
Siemens · LOGO! 12/24RCEversion=V8.3 <*
Siemens · LOGO! 12/24RCEoversion=V8.3 <*
Siemens · LOGO! 24RCEversion=V8.3 <*
Siemens · SIPLUS LOGO! 24CEoversion=V8.3 <*
Siemens · LOGO! 24RCEoversion=V8.3 <*
Siemens · LOGO! 230RCEversion=V8.3 <*
Siemens · SIPLUS LOGO! 24RCEversion=V8.3 <*
Siemens · SIPLUS LOGO! 230RCEoversion=V8.3 <*
Siemens · SIPLUS LOGO! 12/24RCEversion=V8.3 <*
Siemens · LOGO! 230RCEoversion=V8.3 <*
Siemens · SIPLUS LOGO! 230RCEversion=V8.3 <*
Siemens · SIPLUS LOGO! 12/24RCEoversion=V8.3 <*

Published CVSS scores

7.6Siemens ProductCERTCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-1319Improper Protection against Electromagnetic Fault Injection (EM-FI)
T1693Modify Firmware

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo