Code execution via unchecked SB2 block count
Published Mar 23, 2022 · Updated Aug 3, 2024
Buffer overflow in NXP LPC55S66 and LPC55S69 ROM 1B allows attackers to execute non-persistent code via a crafted SB2 update. The ROM parser copies up to the untrusted m_keyBlobBlock value into a fixed global buffer before signature verification instead of stopping after the 128-byte header. Exploitation requires SB2 loading through ISP, SPI recovery, or the update ROM API; normal authenticated secure boot is not exposed.
Summary
What happened
Buffer overflow in NXP LPC55S66 and LPC55S69 ROM 1B allows attackers to execute non-persistent code via a crafted SB2 update. The ROM parser copies up to the untrusted m_keyBlobBlock value into a fixed global buffer before signature verification instead of stopping after the 128-byte header. Exploitation requires SB2 loading through ISP, SPI recovery, or the update ROM API; normal authenticated secure boot is not exposed.
The record
- CVE
- CVE-2022-22819
- Published
- Mar 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Oxide LPC55S69 SB2 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