Skip to content
Fencer Intel
critical 9.1

CVE-2022-23066 json

Solana rBPF - Incorrect Calculation in sdiv instruction

published 4y ago modified 4mo ago also GHSA-9qmm-4mfr-r3wj , EUVD-2022-3433

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io solana_rbpf 0.2.28

Is CVE-2022-23066 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.52% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • whitesourcesoftware.com https://www.whitesourcesoftware.com/vulnerability-database/CVE-2022-23066 referenced PoC, tagged "exploit" by a source, unverified
  • blocksecteam.medium.com https://blocksecteam.medium.com/how-a-critical-bug-in-solana-network-was-detected-and-timely-patched-a701870e1324 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:N/I:P/A:P
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
crates.io solana_rbpf
>=0.2.26, <0.2.28
0.2.28

Affected products

  • solana-labs rbpf

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.