MCU code execution via unchecked I2C length
Published Jan 1, 2024 · Updated Sep 9, 2024
Buffer overflow in STMicroelectronics STSAFE-A1xx middleware before 3.3.7 allows physically proximate attackers to execute MCU code. StSafeA_ReceiveBytes trusts a response length read from I2C data and passes it to a second HwCtx.BusRecv call without checking the 523-byte output buffer. Exploitation requires interception or injection of I2C responses between the MCU and STSAFE-A110, enabling code execution in firmware derived from affected sample applications.
Summary
What happened
Buffer overflow in STMicroelectronics STSAFE-A1xx middleware before 3.3.7 allows physically proximate attackers to execute MCU code. StSafeA_ReceiveBytes trusts a response length read from I2C data and passes it to a second HwCtx.BusRecv call without checking the 523-byte output buffer. Exploitation requires interception or injection of I2C responses between the MCU and STSAFE-A110, enabling code execution in firmware derived from affected sample applications.
The record
- CVE
- CVE-2023-50096
- Published
- Jan 1, 2024
- Updated
- Sep 9, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 2024CVE publishedPublication date reported by the CVE source.
- Sep 9, 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
- StSafeA_ReceiveBytes buffer-overflow 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