# CVE-2007-4739: Security feature bypass in n/a

> Remote attackers can bypass signature verification in reprepro by using an unknown key, allowing distribution of malicious repository updates.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4739, DSA-1394-1, GHSA-w7wf-m6xr-x5x5

## What is CVE-2007-4739?

CVE-2007-4739 is a medium-severity vulnerability in n/a, published on 6 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

reprepro 1.3.0 through 2.2.3 does not properly verify signatures when updating repositories, which allows remote attackers to construct and distribute an ostensibly valid Release.gpg file by signing it with an unknown key, related to the update command.

Weakness: CWE-264

## Which versions are affected by CVE-2007-4739?

It affects 1 product.


Products: Debian Reprepro.

## How do I fix CVE-2007-4739?

Upgrade to a fixed version.

## Is CVE-2007-4739 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4739 and fix it if it is affected.

What it is: CVE-2007-4739 is a medium-severity vulnerability in n/a, published on 6 Sep 2007. 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-2007-4739 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-2007-4739/ (Markdown: https://insights.sbomify.com/CVE-2007-4739/index.md)
```

## Sources

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

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