Memory corruption via transport error mishandling
Published Nov 13, 2024 · Updated Nov 27, 2024
Buffer overflow in Arm SCP-firmware 2.11.0 through 2.15.0 allows attackers controlling an Application Processor to corrupt SCP memory. The transport_message_handler function mishandles an error condition during AP-to-SCP transport processing, causing data to exceed its destination buffer. Reachability requires control of the Application Processor and interaction with the SCP transport path; Arm has not disclosed the exact post-overflow consequence.
Summary
What happened
Buffer overflow in Arm SCP-firmware 2.11.0 through 2.15.0 allows attackers controlling an Application Processor to corrupt SCP memory. The transport_message_handler function mishandles an error condition during AP-to-SCP transport processing, causing data to exceed its destination buffer. Reachability requires control of the Application Processor and interaction with the SCP transport path; Arm has not disclosed the exact post-overflow consequence.
The record
- CVE
- CVE-2024-9413
- Published
- Nov 13, 2024
- Updated
- Nov 27, 2024
- Vendor
- Arm
- Product
- SCP-firmware
- Classifications
- CWE-755
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 27, 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=2.11.0 <=2.15.0
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