Red Hat Enterprise Linux 7: Double Free
CVE-2024-2002 is a high-severity double free vulnerability in Red Hat Enterprise Linux 7 from Red Hat, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 1.09% chance of exploitation within 30 days, higher than 66% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Libdwarf to 0.9.2 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat Enterprise Linux 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Libdwarf Project | Libdwarf | 0.1.0 up to, but not including, 0.9.2 | 0.9.2 |
| Red Hat | Enterprise Linux | 7.0; 8.0 | Not stated |
| Fedora Project | Fedora | 40 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (redhat.com).
Official description
A double-free vulnerability was found in libdwarf. In a multiply-corrupted DWARF object, libdwarf may try to dealloc(free) an allocation twice, potentially causing unpredictable and various results.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Double Free
The product calls free() twice on the same memory address.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
- Use a static analysis tool to find double free instances.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- access.redhat.com/security/cve/CVE-2024-2002Third Party Advisory
- github.com/davea42/libdwarf-code/blob/main/bugxml/data.txtThird Party Advisory
Other references
Other vulnerabilities in Red Hat Enterprise Linux 7
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.9 High severity
- 7.3 High severity
- 7.5 High severity
Recent Double Free vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
- 7.5 High severity
Spotted an error? Tell us.