Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-r864-28pw-8682

HIGH

Harbor fails to validate the user permissions when updating p2p preheat policies

Also known asBIT-harbor-2022-31668CVE-2022-31668GHSA-3wpx-625q-22j7GO-2024-3268
Published
Nov 14, 2024
Updated
Dec 12, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk21th percentile+0.24%
0.00%0.27%0.53%0.80%0.1%0.3%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected
🐹github.com/goharbor/harbor🐹github.com/goharbor/harbor🐹github.com/goharbor/harbor/src

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies configured in other projects.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/goharbor/harbor2.0.0&&< 2.4.32.4.3
🐹Gogithub.com/goharbor/harbor2.5.0&&< 2.5.22.5.2
🐹Gogithub.com/goharbor/harbor/srcall versions0.0.0-20220630175814-b4ef1db

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/goharbor/harbor. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/goharbor/harbor to 2.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r864-28pw-8682 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-r864-28pw-8682 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r864-28pw-8682. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies configured in other projects.
O3 Security · Impact-Aware SCA

Is GHSA-r864-28pw-8682 in your dependencies?

O3 detects GHSA-r864-28pw-8682 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-r864-28pw-8682: harbor (High 7.4) | O3 Security