Cross-site Request Forgery (CSRF) Affecting harbor-2.12 package, versions <2.12.2-r10
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Cross-site Request Forgery (CSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-CHAINGUARDLATEST-HARBOR212-9749398
- published18 Apr 2025
- disclosed15 Apr 2025
Introduced: 15 Apr 2025
NewCVE-2025-24358 (opens in a new tab)How to fix?
Upgrade Chainguard harbor-2.12 to version 2.12.2-r10 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream harbor-2.12 package and not the harbor-2.12 package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
gorilla/csrf provides Cross Site Request Forgery (CSRF) prevention middleware for Go web applications & services. Prior to 1.7.2, gorilla/csrf does not validate the Origin header against an allowlist. Its executes its validation of the Referer header for cross-origin requests only when it believes the request is being served over TLS. It determines this by inspecting the r.URL.Scheme value. However, this value is never populated for "server" requests per the Go spec, and so this check does not run in practice. This vulnerability allows an attacker who has gained XSS on a subdomain or top level domain to perform authenticated form submissions against gorilla/csrf protected targets that share the same top level domain. This vulnerability is fixed in 1.7.2.