# CVE-2014-0478: Supply chain in n/a

> Man-in-the-middle attackers can install malicious Trojan horse packages by bypassing APT source package signature validation.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0478, DSA-2958-1, GHSA-3h3c-x5j6-p285, UBUNTU-CVE-2014-0478, USN-2246-1

## What is CVE-2014-0478?

CVE-2014-0478 is a medium-severity vulnerability in n/a, published on 17 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

APT before 1.0.4 does not properly validate source packages, which allows man-in-the-middle attackers to download and install Trojan horse packages by removing the Release signature.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-0478?

It affects 1 product.


Products: Debian Advanced Package Tool.

## How do I fix CVE-2014-0478?

Upgrade to a fixed version.

## Is CVE-2014-0478 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1358](https://insights.sbomify.com/CVE-2009-1358/): Security feature bypass in n/a (critical 10.0)
- [CVE-2009-1300](https://insights.sbomify.com/CVE-2009-1300/): Denial of service in n/a (critical 10.0)
- [CVE-2014-0487](https://insights.sbomify.com/CVE-2014-0487/): Security feature bypass in n/a (high 7.5)
- [CVE-2014-0489](https://insights.sbomify.com/CVE-2014-0489/): Code injection in n/a (high 7.5)
- [CVE-2014-0490](https://insights.sbomify.com/CVE-2014-0490/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0478 and fix it if it is affected.

What it is: CVE-2014-0478 is a medium-severity vulnerability in n/a, published on 17 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0478 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-2014-0478/ (Markdown: https://insights.sbomify.com/CVE-2014-0478/index.md)
```

## Sources

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

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