# CVE-2023-36326: Integer overflow in n/a

> Attackers can execute arbitrary code, escalate privileges, or cause denial of service via an integer overflow in the RELIC library's bn_grow function.

- **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:** 1 Sep 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-fr5q-2jxw-x8hg

## What is CVE-2023-36326?

CVE-2023-36326 is a critical vulnerability in n/a, published on 1 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer Overflow vulnerability in RELIC before commit 34580d840469361ba9b5f001361cad659687b9ab, allows attackers to execute arbitrary code, cause a denial of service, and escalate privileges when calling realloc function in bn_grow function.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Relic Project Relic.

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

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

## Is CVE-2023-36326 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-36327](https://insights.sbomify.com/CVE-2023-36327/): Integer overflow in n/a (critical 9.8)
- [CVE-2023-51939](https://insights.sbomify.com/CVE-2023-51939/): Information disclosure in n/a (high 8.8)
- [CVE-2020-36316](https://insights.sbomify.com/CVE-2020-36316/): Memory corruption in n/a (medium 5.5)
- [CVE-2020-36315](https://insights.sbomify.com/CVE-2020-36315/): Weak cryptography in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36326 is a critical vulnerability in n/a, published on 1 Sep 2023. 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-2023-36326 in the wild and no public exploit code.

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

## Sources

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

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