Local privilege escalation via MPU-wrapper ROP
Published Mar 7, 2024 · Updated Aug 28, 2024
Improper access control in FreeRTOS Kernel 10.6.1 and earlier allows local users to gain kernel privileges through injected ROP code. The affected MPU wrapper inadequately isolates privileged system-call execution from attacker-controlled return-oriented control flow. Exploitation requires a separate code-injection flaw on an ARMv7-M MPU port or an ARMv8-M port with configENABLE_MPU set to 1.
Summary
What happened
Improper access control in FreeRTOS Kernel 10.6.1 and earlier allows local users to gain kernel privileges through injected ROP code. The affected MPU wrapper inadequately isolates privileged system-call execution from attacker-controlled return-oriented control flow. Exploitation requires a separate code-injection flaw on an ARMv7-M MPU port or an ARMv8-M port with configENABLE_MPU set to 1.
The record
- CVE
- CVE-2024-28115
- Published
- Mar 7, 2024
- Updated
- Aug 28, 2024
- Vendor
- FreeRTOS
- Product
- FreeRTOS Kernel
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 7, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=0 <10.6.2
- Affected versionversion=< 10.6.2
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