# CVE-2008-3323: Code injection in n/a

> Remote attackers can execute arbitrary code by providing a malicious package list to the Cygwin setup utility, which fails to verify package authenticity.

- **Severity:** High 7.6 (`AV:N/AC:H/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:** 28 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v2m6-98xf-3xq5

## What is CVE-2008-3323?

CVE-2008-3323 is a high-severity code injection vulnerability in n/a, published on 28 Jul 2008. 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

setup.exe before 2.573.2.3 in Cygwin does not properly verify the authenticity of packages, which allows remote Cygwin mirror servers or man-in-the-middle attackers to execute arbitrary code via a package list containing the MD5 checksum of a Trojan horse package.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-3323?

It affects 1 product.


Products: Redhat Cygwin.

## How do I fix CVE-2008-3323?

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

## Is CVE-2008-3323 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6181](https://insights.sbomify.com/CVE-2007-6181/): Memory corruption in n/a (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3323 and fix it if it is affected.

What it is: CVE-2008-3323 is a high-severity code injection vulnerability in n/a, published on 28 Jul 2008. 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-2008-3323 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-2008-3323/ (Markdown: https://insights.sbomify.com/CVE-2008-3323/index.md)
```

## Sources

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

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