# CVE-2016-1541: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted ZIP archives due to a heap-based buffer overflow in libarchive.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 May 2016
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2016-1541, DEBIAN-CVE-2016-1541, DSA-3574-1, GHSA-w2vf-7r3f-2gg2, MGASA-2016-0179, SUSE-SU-2016:1588-1, UBUNTU-CVE-2016-1541

## What is CVE-2016-1541?

CVE-2016-1541 is a high-severity memory corruption vulnerability in Libarchive Libarchive, published on 7 May 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the zip_read_mac_metadata function in archive_read_support_format_zip.c in libarchive before 3.2.0 allows remote attackers to execute arbitrary code via crafted entry-size values in a ZIP archive.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-1541?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libarchive` | SUSE:Linux Enterprise Desktop 12 | All versions | 3.1.2-12.1 |
| `libarchive` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 3.1.2-12.1 |
| `libarchive` | SUSE:Linux Enterprise Server 12 | All versions | 3.1.2-12.1 |
| `libarchive` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 3.1.2-12.1 |
| `libarchive` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 3.1.2-12.1 |
| `libarchive` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 3.1.2-12.1 |
| `libarchive` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 3.1.2-12.1 |
| `libarchive` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 3.1.2-12.1 |

Products: Libarchive Libarchive.

## How do I fix CVE-2016-1541?

Upgrade to a fixed version.

## Is CVE-2016-1541 being exploited?

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

## 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-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)
- [CVE-2024-48958](https://insights.sbomify.com/CVE-2024-48958/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1541 and fix it if it is affected.

What it is: CVE-2016-1541 is a high-severity memory corruption vulnerability in Libarchive Libarchive, published on 7 May 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-1541 in the wild and no public exploit code.

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-2016-1541/ (Markdown: https://insights.sbomify.com/CVE-2016-1541/index.md)
```

## Sources

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

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