RUSTSEC-2020-0063 crate has been renamed to `safe-nd`
Not scored
Published
Check this codebase for RUSTSEC-2020-0063 and fix it if it is affected.
What it is: RUSTSEC-2020-0063 is a vulnerability in safe-nd, published on 2 Nov 2020.
Exploitation: There is no known exploitation of RUSTSEC-2020-0063 in the wild and no public exploit code.
Affected packages and fixed versions:
- safe-nd (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/RUSTSEC-2020-0063/ (Markdown: https://insights.sbomify.com/RUSTSEC-2020-0063/index.md)
The crate has been renamed to sn_data_types, requiring users to update their dependencies to the new package name.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is RUSTSEC-2020-0063?
RUSTSEC-2020-0063 is a vulnerability in safe-nd, published on 2 Nov 2020.
Official description
This crate has been renamed from safe-nd to sn_data_types.
The new repository location is:
<https://github.com/maidsafe/sn_data_types>
Which versions are affected by RUSTSEC-2020-0063?
1 open source package ship an affected version, including safe-nd.
| Package | Affected | Fixed in |
|---|---|---|
safe-nd crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2020-0063?
No fix has been published for RUSTSEC-2020-0063 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2020-0063 being exploited?
There is no known exploitation of RUSTSEC-2020-0063 in the wild and no public exploit code.