# CVE-2021-45695: Incorrect reliance on Trait memory layout in mopa

> The mopa crate incorrectly relies on trait memory layout, potentially allowing arbitrary code execution or ASLR bypass in Rust applications.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2gxj-qrp2-53jv, GHSA-8mv5-7x95-7wcf, RUSTSEC-2021-0095

## What is CVE-2021-45695?

CVE-2021-45695 is a critical memory corruption vulnerability in n/a, published on 26 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the mopa crate through 2021-06-01 for Rust. It incorrectly relies on Trait memory layout, possibly leading to future occurrences of arbitrary code execution or ASLR bypass.

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

5 open source packages ship an affected version, including mopa. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mopa` | crates.io | All versions to 0.2.2 | None |
| `mopa` | crates.io | All versions to 0.2.2 | None |
| `mopa` | crates.io | All versions to 0.2.2 | None |
| `mopa` | crates.io | All versions to 0.2.2 | None |
| `mopa` | crates.io | From 0.0.0-0 | None |

Products: Mopa Project Mopa.

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

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

## Is CVE-2021-45695 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-45695 is a critical memory corruption vulnerability in n/a, published on 26 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-45695 in the wild and no public exploit code.

Affected packages and fixed versions:
- mopa (crates.io): affected all versions up to 0.2.2; no fix listed
- mopa (crates.io): affected all versions up to 0.2.2; no fix listed
- mopa (crates.io): affected all versions up to 0.2.2; no fix listed
- mopa (crates.io): affected all versions up to 0.2.2; no fix listed
- mopa (crates.io): affected from 0.0.0-0; no fix listed

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-45695/ (Markdown: https://insights.sbomify.com/CVE-2021-45695/index.md)
```

## Sources

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

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