Volcano: Webhook server vulnerable to OOM due to unbounded HTTP request body size
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.14.2, 1.13.3, 1.12.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Volcano is a Kubernetes-native batch scheduling system. Prior to v1.14.2, v1.13.3, and v1.12.4, the Volcano webhook server does not enforce a size limit on incoming HTTP request bodies. Any in-cluster pod that can reach the webhook endpoint may send an arbitrarily large request body, potentially causing the webhook server to be killed by OOM. All Volcano deployments with the webhook server exposed to in-cluster traffic are affected. This vulnerability is fixed in v1.14.2, v1.13.3, and v1.12.4.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- volcano-sh volcano
From 1.14.0-alpha.0 · fixed in 1.14.2; From 1.13.0 · fixed in 1.13.3; fixed in 1.12.4
- volcano.sh/volcanoGo
fixed in 1.12.4
- volcano.sh/volcanoGo
From 1.13.0 · fixed in 1.13.3
- volcano.sh/volcanoGo
From 1.14.0 · fixed in 1.14.2
- volcano.sh/volcanoGo
fixed in 1.12.4; From 1.13.0 · fixed in 1.13.3; From 1.14.0 · fixed in 1.14.2