Skip to content
Fencer Vulns
medium 5.5

CVE-2024-0911 json

Indent: heap-based buffer overflow in set_buf_break()

published 2024-02-06 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-16693

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

A flaw was found in indent, a program for formatting C code. This issue may allow an attacker to trick a user into processing a specially crafted file to trigger a heap-based buffer overflow, causing the application to crash.

Patch / fix

  • indent Debian 12 2.2.12-4+deb12u3
  • indent Debian 14, Debian 13 2.2.13-4

debian advisories DEBIAN-CVE-2024-0911

  • indent SLE Software Development Kit 12 SP5 2.2.10-38.9.1
  • indent SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 2.2.11-150000.3.9.1

suse advisories SUSE-SU-2024:1134-1SUSE-SU-2024:0965-1

  • indent openSUSE Tumbleweed 2.2.13-3.1

opensuse advisories openSUSE-SU-2024:13700-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-0911 updated cvss 5.5

indent: heap-based buffer overflow in set_buf_break()

  • Red Hat Enterprise Linux 6 indent Red Hat Enterprise Linux 7 indent
    affected: workaround, no fix planned “Do not process untrusted files with the indent program.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.