# CVE-2021-41614: Privilege escalation in n/a

> Unauthorized user programs can read and write the Exception Program Counter Register in OpenRISC mor1kx processors, enabling privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-c5gr-hg39-gr5m

## What is CVE-2021-41614?

CVE-2021-41614 is a high-severity vulnerability in n/a, published on 18 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the controller unit of the OpenRISC mor1kx processor. The read/write access permissions to the Exception Program Counter Register (EPCR) are not implemented correctly. User programs from an unauthorized privilege level can make read/write accesses to EPCR.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2021-41614?

It affects 1 product.


Products: Openrisc Mor1kx Firmware.

## How do I fix CVE-2021-41614?

No fix has been published for CVE-2021-41614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41614 being exploited?

There is no known exploitation of CVE-2021-41614 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-41612](https://insights.sbomify.com/CVE-2021-41612/): Other in n/a (high 8.8)
- [CVE-2021-41613](https://insights.sbomify.com/CVE-2021-41613/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41614 and fix it if it is affected.

What it is: CVE-2021-41614 is a high-severity vulnerability in n/a, published on 18 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41614 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-41614/ (Markdown: https://insights.sbomify.com/CVE-2021-41614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41614
- OSV: https://osv.dev/vulnerability/CVE-2021-41614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-41614/
Summaries are generated and may contain mistakes; the official description above is the record.