CVE-2022-38580

Workarounds

Use dropRequestHeader("X-Skipper-Proxy") filter

References

https://github.com/zalando/skipper/releases/tag/v0.13.237

For more information

If you have any questions or comments about this advisory:

• Open an issue in https://github.com/zalando/skipper/issues/new/choose
• Chat with us in slack: https://app.slack.com/client/T029RQSE6/C82Q5JNH5

Skipper prior to version v0.13.236 is vulnerable to server-side request forgery (SSRF). An attacker can exploit a vulnerable version of proxy to access the internal metadata server or other unauthenticated URLs by adding an specific header (X-Skipper-Proxy) to the http request.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2022-38580 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. 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 (0.13.237); upgrading removes the vulnerable code path.

Kodem intelligence

The problem was patched in version https://github.com/zalando/skipper/releases/tag/v0.13.237.
Users need to upgrade to skipper >=v0.13.237.

1. What is CVE-2022-38580? CVE-2022-38580 is a critical-severity server-side request forgery (SSRF) vulnerability in github.com/zalando/skipper (go), affecting versions < 0.13.237. It is fixed in 0.13.237. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2022-38580? CVE-2022-38580 has a CVSS score of 9.8 (Critical). 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/zalando/skipper are affected by CVE-2022-38580? github.com/zalando/skipper (go) versions < 0.13.237 is affected.
4. Is there a fix for CVE-2022-38580? Yes. CVE-2022-38580 is fixed in 0.13.237. Upgrade to this version or later.
5. Is CVE-2022-38580 exploitable, and should I be worried? Whether CVE-2022-38580 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-2022-38580 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-2022-38580? Upgrade github.com/zalando/skipper to 0.13.237 or later.