# CVE-2017-13707: Privilege escalation in n/a

> Attackers can gain root privileges by exploiting sudo access to the vi editor to modify critical system files in Replibit Backup Manager.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9chv-jmmr-4pmp

## What is CVE-2017-13707?

CVE-2017-13707 is a critical vulnerability in n/a, published on 27 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Privilege escalation in Replibit Backup Manager earlier than version 2017.08.04 allows attackers to gain root privileges via sudo command execution. The vi program can be accessed through sudo, in order to navigate the filesystem and modify a critical file such as /etc/passwd.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-13707?

It affects 1 product.


Products: Axcient Replibit.

## How do I fix CVE-2017-13707?

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

## Is CVE-2017-13707 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13707 and fix it if it is affected.

What it is: CVE-2017-13707 is a critical vulnerability in n/a, published on 27 Aug 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-2017-13707 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-2017-13707/ (Markdown: https://insights.sbomify.com/CVE-2017-13707/index.md)
```

## Sources

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

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