# CVE-2005-3831: Memory corruption in n/a

> A stack-based buffer overflow in CxZIP60.dll allows attackers to execute arbitrary code via a malicious ZIP archive with a long filename.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j4rh-674v-8884

## What is CVE-2005-3831?

CVE-2005-3831 is a medium-severity memory corruption vulnerability in n/a, published on 26 Nov 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in (1) CxZIP60.dll and (2) CxZIP60u.dll, as used in SpeedProject products including (a) ZipStar 5.0 Build 4285, (b) Squeez 5.0 Build 4285, and (c) SpeedCommander 11.0 Build 4430 and 10.51 Build 4430, allows user-assisted attackers to execute arbitrary code via a ZIP archive containing a long filename.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2005-3831?

It affects 3 products.


Products: Speedproject Speedcommander, Speedproject Squeez, Speedproject Zipstar.

## How do I fix CVE-2005-3831?

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

## Is CVE-2005-3831 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2085](https://insights.sbomify.com/CVE-2006-2085/): Memory corruption in n/a (medium 5.1)
- [CVE-2005-3832](https://insights.sbomify.com/CVE-2005-3832/): Memory corruption in n/a (medium 5.1)
- [CVE-2006-0890](https://insights.sbomify.com/CVE-2006-0890/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3831 and fix it if it is affected.

What it is: CVE-2005-3831 is a medium-severity memory corruption vulnerability in n/a, published on 26 Nov 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-3831 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-2005-3831/ (Markdown: https://insights.sbomify.com/CVE-2005-3831/index.md)
```

## Sources

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

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