A critical code injection vulnerability in BentoML allows attackers to achieve arbitrary command execution during the containerization process, posing a severe risk to build pipelines.

The vulnerability stems from improper input sanitization in the docker.system_packages field of bentofile.yaml, where attacker controlled strings are directly interpolated into Dockerfile RUN commands. This allows an unauthenticated attacker to execute arbitrary commands during the bentoml containerize or docker build process.

The ability to execute arbitrary commands during the build phase provides an attacker with complete control over the containerization environment. This could lead to the injection of malicious code into production images, resulting in supply chain compromise, data exfiltration, or unauthorized system access. Given the CVSS score of 7.8, this flaw represents a significant risk to the integrity of software delivery pipelines and downstream deployments.

Immediate Action: Update the BentoML library to version 1.4.37 or later to implement the necessary sanitization of the system_packages field.

Proactive Monitoring: Monitor CI/CD build logs for unusual or unexpected package installation commands and verify that build configurations adhere to strictly defined, non-interpolated inputs.

Compensating Controls: Restrict access to bentofile.yaml configuration files to authorized personnel only and ensure that build environments are isolated with minimal privileges to limit the impact of potential command injection.

Public Exploit Available: No (Exploit available: unknown)

The risk posed by this code injection vulnerability is substantial due to its potential to subvert the software supply chain. Organizations utilizing BentoML must prioritize updating to version 1.4.37 immediately to prevent malicious command execution within their container build environments. Failure to patch allows for the potential injection of backdoors or malicious payloads directly into containerized applications.