Unauthorized EPCR access via missing privilege check
Published Apr 18, 2023 · Updated Feb 6, 2025
Incorrect register permissions in the controller of OpenRISC mor1kx allow local users to read and write the supervisor-only EPCR. The logic in rtl/verilog/mor1kx_ctrl_cappuccino.v accepts l.mfspr and l.mtspr operations on EPCR after entry into user mode instead of enforcing supervisor privilege. Local user-mode code can therefore inspect or alter the saved exception return address and violate the processor privilege boundary.
Summary
What happened
Incorrect register permissions in the controller of OpenRISC mor1kx allow local users to read and write the supervisor-only EPCR. The logic in rtl/verilog/mor1kx_ctrl_cappuccino.v accepts l.mfspr and l.mtspr operations on EPCR after entry into user mode instead of enforcing supervisor privilege. Local user-mode code can therefore inspect or alter the saved exception return address and violate the processor privilege boundary.
The record
- CVE
- CVE-2021-41614
- Published
- Apr 18, 2023
- Updated
- Feb 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 18, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 2025Record 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
- EPCR user-mode trigger programproof 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