# CVE-2024-0684: Coreutils: heap overflow in split --line-bytes with very long lines

> A heap overflow in GNU coreutils split command allows attackers to cause a denial of service via crafted long lines.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2024
- **Updated:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2024-0684, AZL-34629, BELL-CVE-2024-0684, DEBIAN-CVE-2024-0684, GHSA-p8pq-6r4w-c75v, openSUSE-SU-2024:13618-1

## What is CVE-2024-0684?

CVE-2024-0684 is a medium-severity memory corruption vulnerability in gnu:coreutils, published on 6 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the GNU coreutils "split" program. A heap overflow with user-controlled data of multiple hundred bytes in length could occur in the line_bytes_split() function, potentially leading to an application crash and denial of service.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-0684?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `coreutils` | openSUSE:Tumbleweed | All versions | 9.4-3.1 |

Products: Gnu Coreutils.

## How do I fix CVE-2024-0684?

Apply the vendor's patch.

## Is CVE-2024-0684 being exploited?

There is no known exploitation of CVE-2024-0684 in the wild and no public exploit code.

Public exploit code:

- Writeup of a heap overflow vulnerability in the GNU coreutils split program. CVE-2024-0684 (github_poc): https://github.com/Valentin-Metz/writeup_split

## Other vulnerabilities in gnu:coreutils

- [CVE-2015-4042](https://insights.sbomify.com/CVE-2015-4042/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-4041](https://insights.sbomify.com/CVE-2015-4041/): Memory corruption in n/a (high 7.8)
- [CVE-2017-18018](https://insights.sbomify.com/CVE-2017-18018/): Race condition in n/a (high 7.1)
- [CVE-2015-1865](https://insights.sbomify.com/CVE-2015-1865/): Race condition in n/a (medium 5.1)
- [CVE-2026-56391](https://insights.sbomify.com/CVE-2026-56391/): Out‑of‑bounds Read in GNU coreutils (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0684 and fix it if it is affected.

What it is: CVE-2024-0684 is a medium-severity memory corruption vulnerability in gnu:coreutils, published on 6 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0684 in the wild and no public exploit code.

Affected product: gnu:coreutils. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-0684/ (Markdown: https://insights.sbomify.com/CVE-2024-0684/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0684
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0684
- OSV: https://osv.dev/vulnerability/CVE-2024-0684

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-0684/
Summaries are generated and may contain mistakes; the official description above is the record.