# CVE-2023-40022: Rizin vulnerable to Integer Overflow in C++ demangler logic

> An integer overflow in the C++ demangler allows attackers to cause a denial of service via crafted binaries.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-92h6-wwc2-53cq

## What is CVE-2023-40022?

CVE-2023-40022 is a high-severity vulnerability in rizinorg rizin, published on 24 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Rizin is a UNIX-like reverse engineering framework and command-line toolset. Versions 0.6.0 and prior are vulnerable to integer overflow in `consume_count` of `src/gnu_v2/cplus-dem.c`. The overflow check is valid logic but, is missing the modulus if the block once compiled. The compiler sees this block as unreachable code since the prior statement is multiplication by 10 and fails to consider overflow assuming the count will always be a multiple of 10. Rizin version 0.6.1 contains a fix for the issue. A temporary workaround would be disabling C++ demangling using the configuration option `bin.demangle=false`.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-40022?

It affects 1 product.


Products: Rizin Rizin.

## How do I fix CVE-2023-40022?

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

## Is CVE-2023-40022 being exploited?

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

## Other vulnerabilities in rizinorg rizin

- [CVE-2024-31668](https://insights.sbomify.com/CVE-2024-31668/): rizin before v0.6.3 is vulnerable to Improper Neutralization of Special Elements via meta_set function in librz/analysis/meta. (critical 9.1)
- [CVE-2021-3674](https://insights.sbomify.com/CVE-2021-3674/): Memory corruption in rizin (high 7.8)
- [CVE-2023-27590](https://insights.sbomify.com/CVE-2023-27590/): Rizin has stack-based buffer overflow when parsing GDB registers profile files (high 7.8)
- [CVE-2022-36039](https://insights.sbomify.com/CVE-2022-36039/): Out-of-bounds write when parsing DEX files in Rizin (high 7.8)
- [CVE-2022-36040](https://insights.sbomify.com/CVE-2022-36040/): Rizin Out-of-bounds Write vulnerability in pyc/marshal.c (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-40022 and fix it if it is affected.

What it is: CVE-2023-40022 is a high-severity vulnerability in rizinorg rizin, published on 24 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-40022 in the wild and no public exploit code.

Affected product: rizinorg rizin. 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-2023-40022/ (Markdown: https://insights.sbomify.com/CVE-2023-40022/index.md)
```

## Sources

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

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