# CVE-2020-13794: Authenticated users can exploit an enumeration vulnerability in Harbor

> Unauthorized actors can access sensitive information in Harbor container registry due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-harbor-2020-13794, GHSA-q9p8-33wc-h432, GO-2022-0865

## What is CVE-2020-13794?

CVE-2020-13794 is a medium-severity vulnerability in n/a, published on 29 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Harbor 1.9.* 1.10.* and 2.0.* allows Exposure of Sensitive Information to an Unauthorized Actor.

Weakness: CWE-862 (Missing Authorization)

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

4 open source packages ship an affected version, including github.com/goharbor/harbor and harbor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/goharbor/harbor` | Go | All versions | 2.0.3 |
| `github.com/goharbor/harbor` | Go | All versions | 2.0.3 |
| `github.com/goharbor/harbor` | Go | All versions | 2.0.3+incompatible |
| `harbor` | Bitnami | From 1.9.0 | 2.0.3 |

Products: Linuxfoundation Harbor.

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

Upgrade github.com/goharbor/harbor to a fixed version for your release line: 2.0.3 or 2.0.3+incompatible.

## Is CVE-2020-13794 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-4404](https://insights.sbomify.com/CVE-2026-4404/): Use of hard coded credentials in GoHarbor Harbor (critical 9.4)
- [CVE-2019-19023](https://insights.sbomify.com/CVE-2019-19023/): Privilege Escalation in Cloud Native Computing Foundation Harbor (high 8.8)
- [CVE-2019-19025](https://insights.sbomify.com/CVE-2019-19025/): Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor (high 8.8)
- [CVE-2017-17697](https://insights.sbomify.com/CVE-2017-17697/): Server-side request forgery in n/a (high 8.6)
- [CVE-2022-31666](https://insights.sbomify.com/CVE-2022-31666/): Harbor fails to validate user permissions while Viewing, updating and deleting Webhook policies (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13794 is a medium-severity vulnerability in n/a, published on 29 Sep 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-13794 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/goharbor/harbor (Go): affected all versions; fixed in 2.0.3
- github.com/goharbor/harbor (Go): affected all versions; fixed in 2.0.3
- github.com/goharbor/harbor (Go): affected all versions; fixed in 2.0.3+incompatible
- harbor (Bitnami): affected from 1.9.0; fixed in 2.0.3

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-13794/ (Markdown: https://insights.sbomify.com/CVE-2020-13794/index.md)
```

## Sources

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

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