# CVE-2021-46102: Integer overflow in solana_rbpf

> An integer overflow in the Solana rBPF library allows attackers to cause denial of service or potentially execute code via crafted ELF files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xwqr-xmgg-j69q

## What is CVE-2021-46102?

CVE-2021-46102 is a high-severity vulnerability in n/a, published on 27 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

From version 0.2.14 to 0.2.16 for Solana rBPF, function "relocate" in the file src/elf.rs has an integer overflow bug because the sym.st_value is read directly from ELF file without checking. If the sym.st_value is rather large, an integer overflow is triggered while calculating the variable "addr" via "addr = (sym.st_value + refd_pa) as u64";

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

2 open source packages ship an affected version, including solana_rbpf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `solana_rbpf` | crates.io | From 0.2.14 | 0.2.17 |
| `solana_rbpf` | crates.io | From 0.2.14 | 0.2.17 |

Products: Solanalabs Rbpf.

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

Upgrade solana_rbpf to 0.2.17 or later.

## Is CVE-2021-46102 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31264](https://insights.sbomify.com/CVE-2022-31264/): Integer overflow in solana_rbpf (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-46102 is a high-severity vulnerability in n/a, published on 27 Jan 2022. 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-46102 in the wild and no public exploit code.

Affected packages and fixed versions:
- solana_rbpf (crates.io): affected from 0.2.14; fixed in 0.2.17
- solana_rbpf (crates.io): affected from 0.2.14; fixed in 0.2.17

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

## Sources

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

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