# CVE-2003-1376: Weak cryptography in n/a

> Local attackers can brute force weak encryption keys in password-protected ZIP files to extract sensitive data.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** No
- **Published:** 19 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m2jc-49g8-v2f9

## What is CVE-2003-1376?

CVE-2003-1376 is a medium-severity vulnerability in n/a, published on 19 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WinZip 8.0 uses weak random number generation for password protected ZIP files, which allows local users to brute force the encryption keys and extract the data from the zip file by guessing the state of the stream coder.

Weakness: CWE-255

## Which versions are affected by CVE-2003-1376?

It affects 1 product.


Products: Winzip Winzip.

## How do I fix CVE-2003-1376?

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

## Is CVE-2003-1376 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6884](https://insights.sbomify.com/CVE-2006-6884/): Memory corruption in n/a (critical 9.3)
- [CVE-2025-1240](https://insights.sbomify.com/CVE-2025-1240/): WinZip 7Z File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability (high 7.8)
- [CVE-2024-8811](https://insights.sbomify.com/CVE-2024-8811/): WinZip Mark-of-the-Web Bypass Vulnerability (high 7.8)
- [CVE-2008-3442](https://insights.sbomify.com/CVE-2008-3442/): Code injection in n/a (high 7.5)
- [CVE-2007-0264](https://insights.sbomify.com/CVE-2007-0264/): Memory corruption in n/a (medium 6.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1376 and fix it if it is affected.

What it is: CVE-2003-1376 is a medium-severity vulnerability in n/a, published on 19 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-1376 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-2003-1376/ (Markdown: https://insights.sbomify.com/CVE-2003-1376/index.md)
```

## Sources

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

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