# CVE-2020-29050: Path traversal in n/a

> Attackers can read arbitrary files from the server filesystem via directory traversal in SphinxSearch using MySQL client operations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** Yes
- **Published:** 7 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-29050, DLA-2882-1, DSA-5036-1, GHSA-4g2j-rgw2-wmrw, MGASA-2022-0110, OESA-2022-1496, UBUNTU-CVE-2020-29050, openSUSE-SU-2022:0046-1, openSUSE-SU-2022:0054-1, openSUSE-SU-2024:11787-1

## What is CVE-2020-29050?

CVE-2020-29050 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 7 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SphinxSearch in Sphinx Technologies Sphinx through 3.1.1 allows directory traversal (in conjunction with CVE-2019-14511) because the mysql client can be used for CALL SNIPPETS and load_file operations on a full pathname (e.g., a file in the /etc directory). NOTE: this is unrelated to CMUSphinx.

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

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sphinx` | openSUSE:Leap 15.3 | All versions | 2.2.11-lp153.2.3.1 |
| `sphinx` | openSUSE:Leap 15.4 | All versions | 2.2.11-lp154.3.3.1 |

Products: Debian Debian Linux, Sphinxsearch Sphinx.

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

Apply the vendor's patch.

## Is CVE-2020-29050 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29050 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 7 Jan 2022. 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-29050 in the wild and no public exploit code.

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

## Sources

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

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