# CVE-2022-37703: Path traversal in n/a

> An attacker can exploit a path traversal flaw in the calcsize SUID binary to determine the existence of arbitrary directories on the filesystem.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2022
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2022-37703, GHSA-j9rc-2hv9-v5v8, UBUNTU-CVE-2022-37703

## What is CVE-2022-37703?

CVE-2022-37703 is a low-severity path traversal vulnerability in n/a, published on 13 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Amanda 3.5.1, an information leak vulnerability was found in the calcsize SUID binary. An attacker can abuse this vulnerability to know if a directory exists or not anywhere in the fs. The binary will use `opendir()` as root directly without checking the path, letting the attacker provide an arbitrary path.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Amanda Amanda.

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

Apply the vendor's patch.

## Is CVE-2022-37703 being exploited?

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

Public exploit code:

- Amanda Information Disclosure bug. (github_poc): https://github.com/MaherAzzouzi/CVE-2022-37703

## Other vulnerabilities in n/a

- [CVE-2002-0901](https://insights.sbomify.com/CVE-2002-0901/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37703 is a low-severity path traversal vulnerability in n/a, published on 13 Sep 2022. 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-37703 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-37703/ (Markdown: https://insights.sbomify.com/CVE-2022-37703/index.md)
```

## Sources

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

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