Skip to content

Cross-site Request Forgery (CSRF) in Cloud Native Computing Foundation Harbor

High severity GitHub Reviewed Published May 18, 2021 to the GitHub Advisory Database • Updated Sep 6, 2024

Package

gomod github.com/goharbor/harbor (Go)

Affected versions

>= 1.7.0, < 1.8.6
>= 1.9.0, < 1.9.3

Patched versions

1.8.6
1.9.3

Description

Cure53 has discovered that the Harbor web interface does not implement protection mechanisms against Cross-Site Request Forgery (CSRF). By luring an authenticated user onto a prepared third-party website, an attacker can execute any action on the platform in the context of the currently authenticated victim.

The vulnerability was immediately fixed by the Harbor team and all supported versions were patched.

Successful exploitation of this issue will lead to 3rd parties executing actions on the platform of behalf of authenticated users and administrators.

If your product uses the affected releases of Harbor, update to version 1.8.6 and 1.9.3 to patch this issue immediately.

https://github.com/goharbor/harbor/releases/tag/v1.8.6
https://github.com/goharbor/harbor/releases/tag/v1.9.3

References

Published by the National Vulnerability Database Mar 20, 2020
Reviewed May 4, 2021
Published to the GitHub Advisory Database May 18, 2021
Last updated Sep 6, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N

EPSS score

0.177%
(55th percentile)

Weaknesses

CVE ID

CVE-2019-19025

GHSA ID

GHSA-rffr-c932-cpxv

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.