Firmware manipulation via non-cryptographic integrity verification
Published Oct 11, 2022 · Updated Aug 3, 2024
Firmware authenticity flaws in Siemens LOGO! 8 BM before 8.3 allow physically proximate attackers to flash manipulated firmware. The firmware update path accepts packages without authenticating them and checks unencrypted firmware integrity only through a non-cryptographic method. Physical access to the update mechanism is required, and exploitation installs attacker-modified firmware, compromising device integrity and availability.
Summary
What happened
Firmware authenticity flaws in Siemens LOGO! 8 BM before 8.3 allow physically proximate attackers to flash manipulated firmware. The firmware update path accepts packages without authenticating them and checks unencrypted firmware integrity only through a non-cryptographic method. Physical access to the update mechanism is required, and exploitation installs attacker-modified firmware, compromising device integrity and availability.
The record
- CVE
- CVE-2022-36360
- Published
- Oct 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Siemens
- Product
- LOGO! 8 BM
- Classifications
- CWE-345, CWE-354, T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
- Affected versionversion=All versions < V8.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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