# CVE-2023-31922: Denial of service in n/a

> A stack overflow in QuickJS allows attackers to cause a denial of service via crafted JavaScript input.

- **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:** No
- **Published:** 12 May 2023
- **Updated:** 24 Jan 2025
- **Also known as:** GHSA-rc5m-84qg-fpjg

## What is CVE-2023-31922?

CVE-2023-31922 is a high-severity denial of service vulnerability in n/a, published on 12 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

QuickJS commit 2788d71 was discovered to contain a stack-overflow via the component js_proxy_isArray at quickjs.c.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Quickjs Project Quickjs.

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

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

## Is CVE-2023-31922 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31922 exists.

## Other vulnerabilities in n/a

- [CVE-2025-62490](https://insights.sbomify.com/CVE-2025-62490/): Use-after-free in js_print_object in QuickJS (high 8.8)
- [CVE-2025-62491](https://insights.sbomify.com/CVE-2025-62491/): Use-after-free in js_std_promise_rejection_check in QuickJS (high 8.8)
- [CVE-2025-69654](https://insights.sbomify.com/CVE-2025-69654/): Denial of service in n/a (high 7.5)
- [CVE-2023-48183](https://insights.sbomify.com/CVE-2023-48183/): Null dereference in n/a (high 7.5)
- [CVE-2020-22876](https://insights.sbomify.com/CVE-2020-22876/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31922 is a high-severity denial of service vulnerability in n/a, published on 12 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31922 exists.

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

## Sources

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

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