CVE-2022-38580 is a critical-severity (CVSS 9.8) Server-Side Request Forgery (SSRF) vulnerability in github.com/zalando/skipper. 1 public exploit reference exists, so weaponization risk is real. A fix is available for github.com/zalando/skipper — see the affected versions and patch details below.
Skipper vulnerable to SSRF via X-Skipper-Proxy
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-38580.
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2022-38580 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/zalando/skipperReal-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
Impact
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.
Patches
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.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/zalando/skipper | all versions | 0.13.237go get github.com/zalando/skipper@v0.13.237 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
X-Skipper-Proxy v0.13.237 - Server Side Request Forgery (SSRF)
by Hosein Vita · Mar 28, 2023
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zalando/skipper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/zalando/skipper to 0.13.237 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-38580 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-38580 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-38580. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-38580 in your dependencies?
O3 Security finds CVE-2022-38580 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.