# CVE-2022-31671: Harbor fails to validate the user permissions when reading job execution logs through the P2P preheat execution logs

> Authenticated users can read all job logs in Harbor by bypassing permission checks on P2P preheat execution logs.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 14 Nov 2024
- **Updated:** 14 Nov 2024
- **Also known as:** BIT-harbor-2022-31671, GHSA-q76q-q8hw-hmpw

## What is CVE-2022-31671?

CVE-2022-31671 is a high-severity missing authorization vulnerability in Harbor, published on 14 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Harbor fails to validate user permissions when reading and updating job execution logs through the P2P preheat execution logs. By sending a request that attempts to read/update P2P preheat execution logs and specifying different job IDs, malicious authenticated users could read all the job logs stored in the Harbor database.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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

7 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 | From 1.0.0 | 1.10.13 |
| `github.com/goharbor/harbor` | Go | From 1.0.0 | 1.10.13 |
| `github.com/goharbor/harbor` | Go | From 2.0.0 | 2.4.3 |
| `github.com/goharbor/harbor` | Go | From 2.0.0 | 2.4.3 |
| `github.com/goharbor/harbor` | Go | From 2.5.0 | 2.5.2 |
| `github.com/goharbor/harbor` | Go | From 2.5.0 | 2.5.2 |
| `harbor` | Bitnami | From 2.0.0 | 2.4.3, 2.5.2 |

Products: Linuxfoundation Harbor.

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

Upgrade github.com/goharbor/harbor to a fixed version for your release line: 1.10.13, 2.4.3 or 2.5.2.

## Is CVE-2022-31671 being exploited?

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

## Other vulnerabilities in Harbor

- [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-2022-31671 and fix it if it is affected.

What it is: CVE-2022-31671 is a high-severity missing authorization vulnerability in Harbor, published on 14 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31671 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/goharbor/harbor (Go): affected from 1.0.0; fixed in 1.10.13
- github.com/goharbor/harbor (Go): affected from 1.0.0; fixed in 1.10.13
- github.com/goharbor/harbor (Go): affected from 2.0.0; fixed in 2.4.3
- github.com/goharbor/harbor (Go): affected from 2.0.0; fixed in 2.4.3
- github.com/goharbor/harbor (Go): affected from 2.5.0; fixed in 2.5.2
- github.com/goharbor/harbor (Go): affected from 2.5.0; fixed in 2.5.2
- harbor (Bitnami): affected from 2.0.0; fixed in 2.4.3, 2.5.2

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

## Sources

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

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