# CVE-2018-14722: Command injection in n/a

> Attackers can execute arbitrary code as root via crafted filesystem labels if auto-maintenance is enabled in btrfsmaintenance.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** Yes
- **Published:** 15 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-14722, GHSA-gvph-5529-3vhw, UBUNTU-CVE-2018-14722, openSUSE-SU-2024:10662-1

## What is CVE-2018-14722?

CVE-2018-14722 is a high-severity command injection vulnerability in n/a, published on 15 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in evaluate_auto_mountpoint in btrfsmaintenance-functions in btrfsmaintenance through 0.4.1. Code execution as root can occur via a specially crafted filesystem label if btrfs-{scrub,balance,trim} are set to auto in /etc/sysconfig/btrfsmaintenance (this is not the default, though).

## Which versions are affected by CVE-2018-14722?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `btrfsmaintenance` | openSUSE:Tumbleweed | All versions | 0.5-2.5 |

Products: Btrfsmaintenance Project Btrfsmaintenance.

## How do I fix CVE-2018-14722?

Apply the vendor's patch.

## Is CVE-2018-14722 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14722 and fix it if it is affected.

What it is: CVE-2018-14722 is a high-severity command injection vulnerability in n/a, published on 15 Aug 2018. 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-2018-14722 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-2018-14722/ (Markdown: https://insights.sbomify.com/CVE-2018-14722/index.md)
```

## Sources

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

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