An attacker can exploit this by supplying a crafted URL where the file extension portion includes shell command substitution syntax (e.g., $(command)). When the application attempts to download or process the document, the underlying shell executes the injected payload before the processing task proceeds. This allows for unauthenticated arbitrary OS command execution on the host running the zerox-dependent service. Given that this component is often used in automated document ingestion pipelines, the impact is significant, potentially leading to full system compromise or lateral movement from the processing environment.

Impact

Successful exploitation allows for arbitrary code execution with the privileges of the application process. This impacts any server or containerized environment utilizing zerox 1.1.20 to process remote documents. Given the nature of command injection in document parsing pipelines, an attacker could potentially exfiltrate sensitive files, pivot into internal network segments, or deploy further malware.

Recommendation

• Upgrade to a version of zerox beyond 1.1.20 that addresses this sanitization flaw.
• Audit logs for process creation events originating from the application process that invoke shell command substitutions or unexpected poppler-related binaries.
• Implement strict input validation for all URLs submitted to the document ingestion pipeline to ensure no shell metacharacters are present.