Intake hat eine Command Injection über shell() Expansion in Parameter Defaults

The core of this vulnerability lies in the automatic expansion of shell() syntax within parameter default values during catalog parsing. An attacker can embed malicious commands within a catalog YAML file using shell(<command>). When a user loads this crafted YAML, the embedded command is executed on the host system. The potential impact is significant, ranging from data exfiltration and system compromise to complete host takeover. This vulnerability resembles other OS Command Injection flaws, where attackers can leverage system utilities and APIs to achieve unauthorized access and control. The blast radius extends to any system processing these malicious catalogs.

Organizations utilizing Intake for data ingestion and catalog management are at risk, particularly those relying on user-supplied catalog sources. Environments with limited input validation or inadequate security controls on catalog processing are especially vulnerable. Shared hosting environments where multiple users can upload catalogs also present a heightened risk.

• python: Inspect Intake logs for unusual process executions or command line arguments related to catalog parsing. Use ps aux | grep intake to monitor running processes and look for unexpected commands. • linux / server: Monitor system logs (e.g., /var/log/syslog, /var/log/auth.log) for suspicious command executions originating from the Intake process. Use auditd to track file access and system calls related to catalog parsing. • generic web: Examine web server access logs for requests to catalog endpoints containing suspicious YAML content. Look for patterns indicative of shell command injection attempts.

1. 2026-03-19Disclosure

   disclosure

1. Reserviert2026-03-18
2. Veröffentlicht2026-03-19
3. Geändert2026-03-25
4. EPSS aktualisiert2026-04-01

The primary mitigation for CVE-2026-33310 is to immediately upgrade to Intake version 2.0.9 or later. If upgrading is not immediately feasible, consider implementing stricter input validation on catalog YAML files to prevent the inclusion of shell() syntax. Employing a Web Application Firewall (WAF) with rules to detect and block requests containing suspicious shell commands within YAML payloads can provide an additional layer of defense. Thoroughly review and sanitize all catalog sources before processing them to minimize the risk of command execution. After upgrading, confirm the fix by attempting to load a test catalog containing a benign shell() command; it should not execute.