# CVE-2022-23066: Solana rBPF - Incorrect Calculation in sdiv instruction

> Incorrect calculation in the sdiv instruction can lead to wrong execution paths, causing token transfer errors and availability issues in Solana rBPF.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** Yes
- **Published:** 9 May 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9qmm-4mfr-r3wj

## What is CVE-2022-23066?

CVE-2022-23066 is a critical vulnerability in solana-labs rbpf, published on 9 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to transfer tokens or not. The vulnerability affects both integrity and may cause serious availability problems.

Weakness: CWE-682 (Incorrect Calculation)

## Which versions are affected by CVE-2022-23066?

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.26 | 0.2.28 |
| `solana_rbpf` | crates.io | From 0.2.26 | 0.2.28 |

Products: Solana Rbpf.

## How do I fix CVE-2022-23066?

Upgrade solana_rbpf to 0.2.28 or later.

## Is CVE-2022-23066 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23066 and fix it if it is affected.

What it is: CVE-2022-23066 is a critical vulnerability in solana-labs rbpf, published on 9 May 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-2022-23066 in the wild and no public exploit code.

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

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

## Sources

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

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