# CVE-2016-10100: Business logic in n/a

> An attacker can overwrite archives during manifest recovery due to flawed duplicate name processing in BorgBackup.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 2 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-10100, GHSA-7rm7-q7fq-4mq4

## What is CVE-2016-10100?

CVE-2016-10100 is a medium-severity vulnerability in n/a, published on 2 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Borg (aka BorgBackup) before 1.0.9 has a flaw in the way duplicate archive names were processed during manifest recovery, potentially allowing an attacker to overwrite an archive.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-10100?

It affects 1 product.


Products: Borg Borg.

## How do I fix CVE-2016-10100?

Upgrade to a fixed version.

## Is CVE-2016-10100 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10100 and fix it if it is affected.

What it is: CVE-2016-10100 is a medium-severity vulnerability in n/a, published on 2 Jan 2017. 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-2016-10100 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-2016-10100/ (Markdown: https://insights.sbomify.com/CVE-2016-10100/index.md)
```

## Sources

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

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