Memory disclosure or crash via unvalidated pixmaps
Published Mar 12, 2021 · Updated Aug 3, 2024
Out-of-bounds read in the fltk crate before 0.15.3 allows attackers to disclose process memory or crash applications via malformed pixmap data. The fltk::image::Pixmap::new constructor accepts malformed pixmap input without validating its structure, allowing reads past the intended bounds. Exploitation requires an application built with the affected crate to pass attacker-controlled pixmap data to this constructor; the bounded consequences are memory disclosure or a process crash.
Summary
What happened
Out-of-bounds read in the fltk crate before 0.15.3 allows attackers to disclose process memory or crash applications via malformed pixmap data. The fltk::image::Pixmap::new constructor accepts malformed pixmap input without validating its structure, allowing reads past the intended bounds. Exploitation requires an application built with the affected crate to pass attacker-controlled pixmap data to this constructor; the bounded consequences are memory disclosure or a process crash.
The record
- CVE
- CVE-2021-28308
- Published
- Mar 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo