# CVE-2022-37705: Privilege escalation in n/a

> A local attacker with backup user privileges can escalate to root by exploiting argument injection in the runtar SUID wrapper.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2023
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2022-37705, GHSA-f6f6-98vp-w8mf, UBUNTU-CVE-2022-37705, openSUSE-SU-2024:12706-1

## What is CVE-2022-37705?

CVE-2022-37705 is a medium-severity vulnerability in n/a, published on 16 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation flaw was found in Amanda 3.5.1 in which the backup user can acquire root privileges. The vulnerable component is the runtar SUID program, which is a wrapper to run /usr/bin/tar with specific arguments that are controllable by the attacker. This program mishandles the arguments passed to tar binary (it expects that the argument name and value are separated with a space; however, separating them with an equals sign is also supported),

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2022-37705?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `amanda` | openSUSE:Tumbleweed | All versions | 3.5.2-3.1 |

Products: Zmanda Amanda.

## How do I fix CVE-2022-37705?

Apply the vendor's patch.

## Is CVE-2022-37705 being exploited?

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

Public exploit code:

- Amanda 3.5.1 second LPE. (github_poc): https://github.com/MaherAzzouzi/CVE-2022-37705

## Other vulnerabilities in n/a

- [CVE-2019-19469](https://insights.sbomify.com/CVE-2019-19469/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2023-30577](https://insights.sbomify.com/CVE-2023-30577/): Command injection in n/a (high 7.8)
- [CVE-2022-37704](https://insights.sbomify.com/CVE-2022-37704/): Command injection in n/a (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37705 and fix it if it is affected.

What it is: CVE-2022-37705 is a medium-severity vulnerability in n/a, published on 16 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-37705 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-2022-37705/ (Markdown: https://insights.sbomify.com/CVE-2022-37705/index.md)
```

## Sources

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

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