# CVE-2024-33263: Denial of service in n/a

> An assertion failure in QuickJS allows attackers to cause a denial of service via crafted JavaScript input.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Apr 2024
- **Updated:** 21 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-33263, GHSA-wq4j-f7v3-vfpp, UBUNTU-CVE-2024-33263

## What is CVE-2024-33263?

CVE-2024-33263 is a medium-severity denial of service vulnerability in n/a, published on 26 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

QuickJS commit 3b45d15 was discovered to contain an Assertion Failure via JS_FreeRuntime(JSRuntime *) at quickjs.c.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2024-33263?

It affects 1 product.


Products: Bellard Quickjs.

## How do I fix CVE-2024-33263?

Apply the vendor's patch.

## Is CVE-2024-33263 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-46687](https://insights.sbomify.com/CVE-2025-46687/): Memory corruption in QuickJS (medium 5.6)
- [CVE-2025-12745](https://insights.sbomify.com/CVE-2025-12745/): QuickJS quickjs.c js_array_buffer_slice buffer over-read (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33263 and fix it if it is affected.

What it is: CVE-2024-33263 is a medium-severity denial of service vulnerability in n/a, published on 26 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33263 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-2024-33263/ (Markdown: https://insights.sbomify.com/CVE-2024-33263/index.md)
```

## Sources

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

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