# CVE-2024-48877: Memory corruption in xls2csv

> A heap buffer overflow in xls2csv allows attackers to execute arbitrary code or cause denial of service via a malicious file.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-48877, GHSA-2x4q-h3hx-hhh6, UBUNTU-CVE-2024-48877

## What is CVE-2024-48877?

CVE-2024-48877 is a high-severity memory corruption vulnerability in xls2csv, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A memory corruption vulnerability exists in the Shared String Table Record Parser implementation in xls2csv utility version 0.95. A specially crafted malformed file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-680 (Integer Overflow to Buffer Overflow)

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

It affects 1 product.


Products: Wagner Xls2csv.

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

Upgrade to a fixed version.

## Is CVE-2024-48877 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48877 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48877 is a high-severity memory corruption vulnerability in xls2csv, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48877 exists.

Affected product: xls2csv. 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-48877/ (Markdown: https://insights.sbomify.com/CVE-2024-48877/index.md)
```

## Sources

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

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