RUSTSEC-2020-0109 stderr is unmaintained; use eprintln instead
Not scored
Published
Check this codebase for RUSTSEC-2020-0109 and fix it if it is affected.
What it is: RUSTSEC-2020-0109 is a vulnerability in stderr, published on 22 Dec 2020.
Exploitation: There is no known exploitation of RUSTSEC-2020-0109 in the wild and no public exploit code.
Affected packages and fixed versions:
- stderr (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-0109/ (Markdown: https://insights.sbomify.com/RUSTSEC-2020-0109/index.md)
The unmaintained stderr crate should be replaced with the standard library eprintln macro to ensure security and maintenance.
- 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-0109?
RUSTSEC-2020-0109 is a vulnerability in stderr, published on 22 Dec 2020.
Official description
The stderr crate is no longer maintained by its current owner.
The author recommends using the eprintln macro from the standard library as a
replacement.
Which versions are affected by RUSTSEC-2020-0109?
1 open source package ship an affected version, including stderr.
| Package | Affected | Fixed in |
|---|---|---|
stderr crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2020-0109?
No fix has been published for RUSTSEC-2020-0109 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2020-0109 being exploited?
There is no known exploitation of RUSTSEC-2020-0109 in the wild and no public exploit code.