Skip to content
Fencer Intel
medium —

GHSA-fwfx-rrv8-crpf 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-0405

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.

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

Patch / fix

  • crates.io rustyscript 0.6.1

Is GHSA-fwfx-rrv8-crpf 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io rustyscript
>=0.4.0, <0.6.1
>=0.3.1-0, <0.6.1
0.6.1

References

Sources

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.