Intake versions prior to 2.0.9 are vulnerable to remote code execution, allowing unauthenticated attackers to execute arbitrary commands on the host system via malicious catalog files.

This vulnerability involves improper neutralization of special elements, specifically OS command and code injection, occurring when Intake automatically parses shell syntax in catalog YAML files. An unauthenticated attacker can trigger this by providing a malicious catalog file to a user or system, resulting in arbitrary code execution upon access.

Successful exploitation allows an attacker to gain full control over the host system, leading to complete compromise of confidentiality, integrity, and availability. With a CVSS score of 8.8, this vulnerability poses a significant risk to organizational infrastructure, particularly where Intake is used to process untrusted data sources or catalogs.

Immediate Action: Upgrade the Intake package to version 2.0.9 or later, which disables shell expansion by default.

Proactive Monitoring: Review application logs and system process trees for suspicious child processes spawned by the Intake service or associated Python environments.

Compensating Controls: Restrict the ingestion of catalog YAML files to trusted sources only and implement sandboxing or containerization to limit the impact of potential command execution on the host OS.

Public Exploit Available: Yes, a public proof-of-concept exists via a GitHub repository.

Given the severity of this remote code execution vulnerability, organizations should prioritize the update to Intake 2.0.9 immediately. Failure to patch allows for potential system takeover, and the existence of public proof-of-concept material increases the likelihood of opportunistic exploitation. Update all affected environments as part of an urgent security maintenance cycle.