Arbitrary code execution via unenforced secure boot
Published Jun 1, 2023 · Updated Jan 10, 2025
Improper firmware verification in Sprecher Automation SPRECON-E PU244x CPU modules allows physically proximate attackers to execute arbitrary code. The i.MX6 High Assurance Boot configuration detects modified firmware and bootloader images but does not enforce the violation, so altered code still boots. Exploitation requires extended physical access and hardware manipulation, and successful code injection grants full control of the device.
Summary
What happened
Improper firmware verification in Sprecher Automation SPRECON-E PU244x CPU modules allows physically proximate attackers to execute arbitrary code. The i.MX6 High Assurance Boot configuration detects modified firmware and bootloader images but does not enforce the violation, so altered code still boots. Exploitation requires extended physical access and hardware manipulation, and successful code injection grants full control of the device.
The record
- CVE
- CVE-2022-4332
- Published
- Jun 1, 2023
- Updated
- Jan 10, 2025
- Vendor
- Sprecher Automation
- Product
- SPRECON-E
- Classifications
- CWE-20, CAPEC-533, T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 2025Record 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
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
- Missing secure-boot proof of conceptproof of concept · demonstrated
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