Service crash via GD2 encoder double free
Published Aug 26, 2021 · Updated Aug 4, 2024
Double-free flaw in LibGD through 2.3.2 allows attackers to trigger a service crash via crafted GD2 image data. The gdImageGd2Ptr path in gd_gd2.c mishandles cleanup while producing GD2 output, releasing allocated memory twice when an error path is reached. The CVE is disputed by the vendor, and exploitation requires a component that processes attacker-influenced GD2 data; reported impact is denial of service without stated confidentiality or integrity loss.
Summary
What happened
Double-free flaw in LibGD through 2.3.2 allows attackers to trigger a service crash via crafted GD2 image data. The gdImageGd2Ptr path in gd_gd2.c mishandles cleanup while producing GD2 output, releasing allocated memory twice when an error path is reached. The CVE is disputed by the vendor, and exploitation requires a component that processes attacker-influenced GD2 data; reported impact is denial of service without stated confidentiality or integrity loss.
The record
- CVE
- CVE-2021-40145
- Published
- Aug 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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.
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