CVE-2019-19025

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

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2019-19025 has a CVSS score of 7.6 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.6, 1.9.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2019-19025? CVE-2019-19025 is a high-severity cross-site request forgery (CSRF) vulnerability in github.com/goharbor/harbor (go), affecting versions >= 1.7.0, < 1.8.6. It is fixed in 1.8.6, 1.9.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2019-19025? CVE-2019-19025 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/goharbor/harbor are affected by CVE-2019-19025? github.com/goharbor/harbor (go) versions >= 1.7.0, < 1.8.6 is affected.
4. Is there a fix for CVE-2019-19025? Yes. CVE-2019-19025 is fixed in 1.8.6, 1.9.3. Upgrade to this version or later.
5. Is CVE-2019-19025 exploitable, and should I be worried? Whether CVE-2019-19025 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2019-19025 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2019-19025?
   • Upgrade github.com/goharbor/harbor to 1.8.6 or later
   • Upgrade github.com/goharbor/harbor to 1.9.3 or later