Snyk a identifié une vulnérabilité d'exécution de code à distance (RCE) dans toutes les versions de Code Agent. La vulnérabilité permet à un attaquant d'exécuter du code arbitraire dans le conteneur Code Agent. Exploitation

Successful exploitation of CVE-2024-21571 grants an attacker the ability to execute arbitrary code within the Code Agent container. This could allow them to steal sensitive data, modify system configurations, or even gain control of the entire deployment environment. The impact is particularly severe if the Code Agent container has access to sensitive resources or is part of a critical infrastructure component. While external exploitation requires specific misconfigurations, internal attackers with access to the cluster could leverage this vulnerability for lateral movement and privilege escalation. The blast radius extends to any systems accessible from the compromised Code Agent container.

Organizations deploying Code Agent within containerized environments, particularly those utilizing shared clusters or cloud-based deployments, are at risk. Legacy configurations with relaxed security policies and those lacking robust network segmentation are especially vulnerable. Environments where the Code Agent container has broad network access or interacts with sensitive data are also at higher risk.

• docker: Inspect container network configurations for unnecessary exposed ports.

docker port <container_id>

• docker: Check for unusual processes running within the Code Agent container.

docker exec -it <container_id> ps aux

• generic web: Monitor Code Agent logs for suspicious activity, such as unexpected command execution or network connections. Look for patterns indicative of code injection attempts. • generic web: Review Docker Compose files or Kubernetes manifests for misconfigured network policies or overly permissive access controls.

1. 2024-12-06Disclosure

   disclosure

1. Réservé2023-12-22
2. Publiée2024-12-06
3. EPSS mis à jour2026-04-02

The primary mitigation for CVE-2024-21571 is to upgrade to a version of Code Agent that includes a fix. However, as of the publication date, no fixed version has been released. Until a fix is available, organizations should focus on hardening their cluster configurations to minimize the risk of exploitation. This includes restricting network access to the Code Agent container and implementing strong authentication and authorization controls. Reviewing and auditing existing configurations is crucial. After upgrading to a fixed version (when available), confirm by attempting to trigger the vulnerable code path and verifying that it is no longer exploitable.