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

> Local attackers can execute arbitrary code by placing a malicious script in the current working directory, affecting Debian systems using apt-listchanges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** Yes
- **Published:** 17 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0302, DSA-1465-2, GHSA-gcfh-ffhx-7mvf

## What is CVE-2008-0302?

CVE-2008-0302 is a high-severity code injection vulnerability in n/a, published on 17 Jan 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in apt-listchanges.py in apt-listchanges before 2.82 allows local users to execute arbitrary code via a malicious apt-listchanges program in the current working directory.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Debian Apt-Listchanges.

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

Upgrade to a fixed version.

## Is CVE-2008-0302 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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