Rust advisories / fltk
Vulnerability HighRUSTSEC-2021-0038 · fltk
RUSTSEC-2021-0038: Multiple memory safety issues
Short answerA security vulnerability in the fltk crate: Multiple memory safety issues. GitHub rates it High. Fixed in 0.15.3: update to a fixed version.
| Crate | fltk |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 0.15.3. |
| Fixed in | 0.15.3 |
| Severity | High (GitHub rating) |
| Published | 2021-03-06 |
| Last changed | 2024-03-15 |
| Also known as | CVE-2021-28306, CVE-2021-28307, CVE-2021-28308, GHSA-5pg8-h4gv-m3p8, GHSA-7qcc-g2m9-8533, GHSA-vjmg-pc8h-p6p8 |
| Affected functions | fltk::image::Pixmap::new, fltk::prelude::WidgetExt::set_label_type, fltk::prelude::WindowExt::set_icon |
What to do
- See which version you have:
cargo tree -i fltk(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p fltk. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplefltk = "0.15.3") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Affected versions contain multiple memory safety issues, such as:
- Setting a multi label type where an image doesn't exist would lead to a NULL pointer dereference.
- Setting a window icon using a non-raster image (which FLTK rasterizes lazily) would lead to a NULL dereference.
- Pixmap constructor would not check for correct pixmaps which could lead to out-of bound reads.
References
- Package: crates.io/crates/fltk
- Advisory: rustsec.org/advisories/RUSTSEC-2021-0038.html
- Report: github.com/MoAlyousef/fltk-rs/issues/519
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?