# GHSA-4mw5-2636-4535: op_panic in the base runtime can force a panic in the runtime's containing thread

> Attackers can crash the host thread and break sandboxing by calling an exposed panic function in the Deno core runtime.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2024
- **Also known as:** RUSTSEC-2024-0403

## What is GHSA-4mw5-2636-4535?

GHSA-4mw5-2636-4535 is a denial of service vulnerability in js-sandbox, published on 18 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions use deno_core releases that expose `Deno.core.ops.op_panic` to the JS runtime in the base core

This function when called triggers a manual panic in the thread containing the runtime, breaking sandboxing

It can be fixed by stubbing out the exposed op:
```javascript
Deno.core.ops.op_panic = (msg) => { throw new Error(msg) };
```

## Which versions are affected by GHSA-4mw5-2636-4535?

3 open source packages ship an affected version, including js-sandbox.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `js-sandbox` | crates.io | All versions to 0.1.6 | None |
| `js-sandbox` | crates.io | All versions to 0.1.6 | None |
| `js-sandbox` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-4mw5-2636-4535?

No fix has been published for GHSA-4mw5-2636-4535 yet. Limit exposure of the affected software until one is available.

## Is GHSA-4mw5-2636-4535 being exploited?

There is no known exploitation of GHSA-4mw5-2636-4535 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4mw5-2636-4535 and fix it if it is affected.

What it is: GHSA-4mw5-2636-4535 is a denial of service vulnerability in js-sandbox, published on 18 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4mw5-2636-4535 in the wild and no public exploit code.

Affected packages and fixed versions:
- js-sandbox (crates.io): affected all versions up to 0.1.6; no fix listed
- js-sandbox (crates.io): affected all versions up to 0.1.6; no fix listed
- js-sandbox (crates.io): affected from 0.0.0-0; no fix listed

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/GHSA-4mw5-2636-4535/ (Markdown: https://insights.sbomify.com/GHSA-4mw5-2636-4535/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4mw5-2636-4535

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4mw5-2636-4535/
Summaries are generated and may contain mistakes; the official description above is the record.