GHSA-4mw5-2636-4535 json
op_panic in the base runtime can force a panic in the runtime's containing thread
published 2y ago modified last yr. also RUSTSEC-2024-0403
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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) }; ```
Is GHSA-4mw5-2636-4535 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | js-sandbox | <=0.1.6 >=0.0.0-0 |
no fix listed |
References
-
github.com
/Bromeon/js-sandbox/issues/31
web, report
-
github.com
/Bromeon/js-sandbox
package
-
rustsec.org
/advisories/RUSTSEC-2024-0403.html
web, advisory
-
crates.io
/crates/js-sandbox
package
Sources
- GitHub Advisory GHSA-4mw5-2636-4535
- OSV RUSTSEC-2024-0403
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.