# CVE-2020-1853: Path traversal in GaussDB 200

> An authenticated attacker can exploit insufficient input validation to traverse directories and download files, leading to information leakage in GaussDB 200.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8g5w-xh3j-7w3x

## What is CVE-2020-1853?

CVE-2020-1853 is a medium-severity path traversal vulnerability in Huawei GaussDB 200, published on 17 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GaussDB 200 with version of 6.5.1 have a path traversal vulnerability. Due to insufficient input path validation, an authenticated attacker can traverse directories and download files to a specific directory. Successful exploit may cause information leakage.

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

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

It affects 1 product.


Products: Huawei Gaussdb 200.

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

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

## Is CVE-2020-1853 being exploited?

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

## Other vulnerabilities in Huawei GaussDB 200

- [CVE-2020-1790](https://insights.sbomify.com/CVE-2020-1790/): Command injection in GaussDB 200 (high 8.8)
- [CVE-2020-1811](https://insights.sbomify.com/CVE-2020-1811/): Command injection in GaussDB 200 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1853 is a medium-severity path traversal vulnerability in Huawei GaussDB 200, published on 17 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1853 in the wild and no public exploit code.

Affected product: Huawei GaussDB 200. 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-1853/ (Markdown: https://insights.sbomify.com/CVE-2020-1853/index.md)
```

## Sources

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

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