CVE-2021-28308
Description
An issue was discovered in the fltk crate before 0.15.3 for Rust. There is an out-of bounds read because the pixmap constructor lacks pixmap input validation.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the fltk crate for Rust before 0.15.3, the pixmap constructor lacks input validation, causing an out-of-bounds read.
CVE-2021-28308: Out-of-bounds read in fltk pixmap constructor
An out-of-bounds read vulnerability exists in the fltk crate for Rust, a set of bindings for the FLTK GUI library. The flaw resides in the pixmap constructor, which does not perform proper input validation when constructing a Pixmap object. This lack of validation can lead to the reading of memory beyond the allocated buffer. The issue is present in versions prior to 0.15.3 [1][2][3].
Attack
Vector and Prerequisites
The vulnerability can be triggered when an attacker is able to supply malformed or specially crafted pixmap data to the Pixmap::new function. While no authentication is required to invoke the vulnerable function, the attacker would need some way to influence the pixmap data processed by the application, such as by providing manipulated image files or through data injection into an interface that uses the pixmap loader. The crate's cross-platform nature makes this issue relevant across Windows, Linux, and macOS when using the bundled FLTK library [1][2][3].
Impact
Successful exploitation of this out-of-bounds read could lead to information disclosure, as an attacker may read sensitive data from adjacent memory regions. Additionally, the behavior could cause a program crash, resulting in a denial of service. The RustSec advisory categorizes this as a memory safety issue with undefined behavior, which can potentially be leveraged for more severe consequences depending on the application's context [3].
Mitigation
The vulnerability has been patched in fltk crate version 0.15.3 and later. Users are advised to update their Cargo.toml dependency to "^1.5" or newer, which includes the fix [1][2][3]. No workarounds are documented; the only recommended mitigation is to upgrade to the patched version.
AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
fltkcrates.io | < 0.15.3 | 0.15.3 |
Affected products
2- fltk/fltkdescription
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4- github.com/advisories/GHSA-vjmg-pc8h-p6p8ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2021-28308ghsaADVISORY
- github.com/MoAlyousef/fltk-rs/issues/519ghsaWEB
- rustsec.org/advisories/RUSTSEC-2021-0038.htmlghsax_refsource_MISCWEB
News mentions
0No linked articles in our index yet.