no cvss
—
- 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
The author of the `stdweb` crate is unresponsive.
Maintained alternatives:
- [`wasm-bindgen`](https://github.com/rustwasm/wasm-bindgen) - [`js-sys`](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/js-sys) - [`web-sys`](https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys)
Patch / fix
- crates.io stdweb 0.4.21-0
Is RUSTSEC-2020-0056 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 | stdweb | >=0.0.0-0, <0.4.21-0 |
0.4.21-0 |
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.