Rust advisories / boxfnonce
UnmaintainedRUSTSEC-2019-0040 · boxfnonce
RUSTSEC-2019-0040: `boxfnonce` obsolete with release of Rust 1.35.0
Short answerNot a bug report: boxfnonce is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | boxfnonce |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2019-06-20 |
| Last changed | 2023-03-12 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2019-0040"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i boxfnonce.
Details from the advisory
This commit marks the boxfnonce crate as obsolete and the GitHub repo has since been archived.
The functionality of boxfnonce has been added to Rust since 1.35.0. Use Box<dyn FnOnce(...) -> ...>.
References
- Package: crates.io/crates/boxfnonce
- Advisory: rustsec.org/advisories/RUSTSEC-2019-0040.html
- Web: github.com/stbuehler/rust-boxfnonce/commit/058ac7e1a7d732076da9d8a37baa66bcb67758d8
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?