# CVE-2012-1163: Integer overflow in n/a

> Remote attackers can execute arbitrary code and leak information by exploiting an integer overflow in libzip via a malicious zip archive.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 12 Jul 2012
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-1163, GHSA-29xg-c3jw-cp68

## What is CVE-2012-1163?

CVE-2012-1163 is a medium-severity vulnerability in n/a, published on 12 Jul 2012. 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

Integer overflow in the _zip_readcdir function in zip_open.c in libzip 0.10 allows remote attackers to execute arbitrary code via the size and offset values for the central directory in a zip archive, which triggers "improper restrictions of operations within the bounds of a memory buffer" and an information leak.

Weakness: CWE-189

## Which versions are affected by CVE-2012-1163?

It affects 1 product.


Products: Nih Libzip.

## How do I fix CVE-2012-1163?

Upgrade to a fixed version.

## Is CVE-2012-1163 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1162](https://insights.sbomify.com/CVE-2012-1162/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1163 and fix it if it is affected.

What it is: CVE-2012-1163 is a medium-severity vulnerability in n/a, published on 12 Jul 2012. 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-2012-1163 in the wild and no public exploit code.

Affected product: n/a. 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-2012-1163/ (Markdown: https://insights.sbomify.com/CVE-2012-1163/index.md)
```

## Sources

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

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