CVE-2020-37239

libbabl 0.1.62 Broken Double Free Detection Memory Safety

Published May 16, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
libbabl 0.1.62 contains a broken double free detection vulnerability that allows attackers to bypass memory safety checks by exploiting signature overwriting in freed chunks. Attackers can call babl_free() twice on the same pointer without triggering detection, as libc's malloc metadata overwrites babl's signature field upon freeing, enabling potential memory corruption and code execution.

Analysis

AI-generated

Technical impact

A double free protection mechanism in libbabl 0.1.62 is ineffective because the library’s internal signature field is overwritten by the underlying malloc implementation when a chunk is freed. This allows an attacker to call babl_free() twice on the same pointer without triggering the library’s detection logic. As described, the flaw can lead to arbitrary memory corruption and the advisory notes the possibility of code execution. The impact is a loss of process integrity and, potentially, confidentiality if sensitive data is accessed during corruption. No explicit confirmation of privilege escalation is provided in the advisory, so that remains an open question.

Affected Systems

The vulnerability affects only the Gegl libbabl component at version 0.1.62. Any application or system linking against this specific library release is vulnerable; other versions or vendors are not listed as affected.

Risk and Exploitability

The CVSS score of 9.3 indicates critical severity. The EPSS score is not available, so the current exploitation probability is unknown. The flaw is not listed in the CISA KEV catalog. The description does not explicitly state an attack vector; however, based on the description, it is inferred that an attacker would need to trigger two consecutive free operations on the same pointer, which typically requires influence over libbabl's memory allocation flow. Successful exploitation would allow memory corruption and potentially arbitrary code execution within the process.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gegl to a libbabl release newer than 0.1.62, which removes the double free detection flaw.
  • If an update cannot be applied, modify the application code to guarantee that babl_free() is invoked only once per allocation and to eliminate logic paths that could lead to a double free.
  • As a temporary defensive measure, employ runtime memory debugging tools or image validation routines to detect malformed data that could trigger the double free before it reaches babl_free().

Generated by OpenCVE AI on May 16, 2026 at 17:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gegl libbabl
Vendors & Products Gegl libbabl
Type Values Removed Values Added
Description libbabl 0.1.62 contains a broken double free detection vulnerability that allows attackers to bypass memory safety checks by exploiting signature overwriting in freed chunks. Attackers can call babl_free() twice on the same pointer without triggering detection, as libc's malloc metadata overwrites babl's signature field upon freeing, enabling potential memory corruption and code execution.
Title libbabl 0.1.62 Broken Double Free Detection Memory Safety
First Time appeared Gegl
Gegl gegl
Weaknesses CWE-415
CPEs cpe:2.3:a:gegl:gegl:0.1.62:*:*:*:*:*:*:*
Vendors & Products Gegl
Gegl gegl
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
May 18, 2026, 6:09 PM
Reserved
May 15, 2026, 2:52 PM
Status
Deferred
Published
May 16, 2026, 4:16 PM
Modified
Sep 29, 2026, 10:10 AM