# CVE-2013-0138: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a crafted ZIP archive in BitZipper.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** No
- **Published:** 22 Apr 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w9gp-m595-7p4f

## What is CVE-2013-0138?

CVE-2013-0138 is a critical memory corruption vulnerability in n/a, published on 22 Apr 2013. 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

BitZipper 2013 before Update 1 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted ZIP archive.

## Which versions are affected by CVE-2013-0138?

It affects 1 product.


Products: Bitberry Software Bitzipper.

## How do I fix CVE-2013-0138?

No fix has been published for CVE-2013-0138 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-0138 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2520](https://insights.sbomify.com/CVE-2006-2520/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0138 and fix it if it is affected.

What it is: CVE-2013-0138 is a critical memory corruption vulnerability in n/a, published on 22 Apr 2013. 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-2013-0138 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-2013-0138/ (Markdown: https://insights.sbomify.com/CVE-2013-0138/index.md)
```

## Sources

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

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