CyberRota Analysis
AI-GeneratedVersions of Jupyter Enterprise Gateway prior to 3.3.0 are vulnerable to YAML injection attacks due to improper handling of untrusted environment variables in Kubernetes manifests. This vulnerability allows attackers to manipulate critical fields and create arbitrary resources, potentially leading to the deployment of privileged pods. Organizations utilizing Jupyter Enterprise Gateway with Apache, Docker, or Kubernetes should prioritize upgrading to version 3.3.0 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions prior to 3.3.0, the server interpolates untrusted environment variables (e.g., KERNEL_XXX) into Kubernetes manifests without YAML-aware escaping, enabling YAML injection attacks. Attackers can inject new fields, overwrite critical fields (e.g., duplicate securityContext keys, where the last one prevails), and inject document boundaries (--- for new documents, ... for end-of-document) to generate multiple resources, potentially creating arbitrary types, such as privileged pods. The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, such as kernel_working_dir that are used when rendering the manifest and are all vectors for YAML injection. This issue has been fixed in version 3.3.0.
Related CVEs
Other vulnerabilities affecting the same vendor(s)