# CVE-2020-9708: GHSL-2020-133: Insufficient validation of user input in resolveRepositoryPath function

> Attackers can traverse directories to access private Git repositories outside the intended root, leading to unauthorized data disclosure.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cgj4-x2hh-2x93

## What is CVE-2020-9708?

CVE-2020-9708 is a medium-severity path traversal vulnerability in Adobe Helix, published on 14 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The resolveRepositoryPath function doesn't properly validate user input and a malicious user may traverse to any valid Git repository outside the repoRoot. This issue may lead to unauthorized access of private Git repositories as long as the malicious user knows or brute-forces the location of the repository.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-24 (Path Traversal: '../filedir')

## Which versions are affected by CVE-2020-9708?

It affects 1 product.


Products: Adobe Git-Server.

## How do I fix CVE-2020-9708?

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

## Is CVE-2020-9708 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9708 and fix it if it is affected.

What it is: CVE-2020-9708 is a medium-severity path traversal vulnerability in Adobe Helix, published on 14 Aug 2020. 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-2020-9708 in the wild and no public exploit code.

Affected product: Adobe Helix. 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-2020-9708/ (Markdown: https://insights.sbomify.com/CVE-2020-9708/index.md)
```

## Sources

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

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