Kernel privilege escalation via signed syscall comparison
Published May 11, 2020 · Updated Sep 16, 2024
Privilege escalation in Zephyr RTOS 1.14.0 through 1.14.1 and 2.1.0 on ARC allows local users to execute code in the kernel. The ARC syscall entry path uses a signed branch-less-than comparison for a user-controlled syscall number, so a negative value passes the upper-bound check. Code execution in an unprivileged user thread on an ARC build with userspace isolation is required, after which the caller gains kernel privileges.
Summary
What happened
Privilege escalation in Zephyr RTOS 1.14.0 through 1.14.1 and 2.1.0 on ARC allows local users to execute code in the kernel. The ARC syscall entry path uses a signed branch-less-than comparison for a user-controlled syscall number, so a negative value passes the upper-bound check. Code execution in an unprivileged user thread on an ARC build with userspace isolation is required, after which the caller gains kernel privileges.
The record
- CVE
- CVE-2020-10027
- Published
- May 11, 2020
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-697, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 11, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=1.14.0 <unspecified
- Affected versionversion=2.1.0 <unspecified
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.
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