# CVE-2025-1632: libarchive bsdunzip.c list null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in libarchive's bsdunzip list function.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 24 Feb 2025
- **Updated:** 24 Feb 2025
- **Also known as:** ALPINE-CVE-2025-1632, AZL-57156, BELL-CVE-2025-1632, DEBIAN-CVE-2025-1632, ECHO-bddc-4b21-dfd5, GHSA-cw9m-pj72-3cj5, JLSEC-2025-242, MINI-c6fq-x5xv-66qw, UBUNTU-CVE-2025-1632

## What is CVE-2025-1632?

CVE-2025-1632 is a medium-severity vulnerability in Libarchive Libarchive, published on 24 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in libarchive up to 3.7.7. It has been classified as problematic. This affects the function list of the file bsdunzip.c. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2025-1632?

It affects 1 product.


Products: Libarchive Libarchive.

## How do I fix CVE-2025-1632?

No fix published yet.

## Is CVE-2025-1632 being exploited?

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

## Other vulnerabilities in Libarchive Libarchive

- [CVE-2024-37407](https://insights.sbomify.com/CVE-2024-37407/): Memory corruption in n/a (critical 9.1)
- [CVE-2016-1541](https://insights.sbomify.com/CVE-2016-1541/): Memory corruption in n/a (high 8.8)
- [CVE-2016-6250](https://insights.sbomify.com/CVE-2016-6250/): Integer overflow in n/a (high 8.6)
- [CVE-2025-5914](https://insights.sbomify.com/CVE-2025-5914/): Libarchive: double free at archive_read_format_rar_seek_data() in archive_read_support_format_rar.c (high 7.8)
- [CVE-2024-48957](https://insights.sbomify.com/CVE-2024-48957/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1632 and fix it if it is affected.

What it is: CVE-2025-1632 is a medium-severity vulnerability in Libarchive Libarchive, published on 24 Feb 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-2025-1632 exists.

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

## Sources

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

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