CVE-2021-21696: Jenkins RCE Vulnerability via Agent Access

CVE-2021-21696 Overview

CVE-2021-21696 is a critical remote code execution vulnerability affecting Jenkins 2.318 and earlier, as well as LTS 2.303.2 and earlier. The vulnerability exists due to improper access control in the FilePath APIs, which fail to limit agent read/write access to the libs/ directory inside build directories. This security flaw allows attackers who have compromised agent processes to replace trusted library code with malicious variants, ultimately resulting in unsandboxed code execution within the Jenkins controller process.

Critical Impact

Attackers with control over Jenkins agent processes can achieve arbitrary code execution on the Jenkins controller by replacing trusted library code, potentially compromising the entire CI/CD pipeline and associated infrastructure.

Affected Products

• Jenkins 2.318 and earlier (weekly releases)
• Jenkins LTS 2.303.2 and earlier (Long-Term Support releases)
• All Jenkins installations using FilePath APIs with agent-to-controller file operations

Discovery Timeline

• 2021-11-04 - CVE-2021-21696 published to NVD
• 2024-11-21 - Last updated in NVD database

Technical Details for CVE-2021-21696

Vulnerability Analysis

This vulnerability stems from a fundamental access control weakness in Jenkins' FilePath API implementation. The FilePath APIs are designed to facilitate file operations between Jenkins agents and the controller. However, prior to the patch, these APIs did not properly restrict agent access to sensitive directories, specifically the libs/ directory within build directories.

The libs/ directory is particularly significant because it contains shared libraries that are trusted and executed within the Jenkins controller's security context. When pipeline builds execute, code from this directory runs without sandbox restrictions, making it a high-value target for attackers.

The attack scenario requires an adversary to first gain control of a Jenkins agent process. This could occur through compromised build scripts, malicious dependencies, or exploiting other vulnerabilities in the agent environment. Once an agent is compromised, the attacker can leverage the unrestricted FilePath APIs to write malicious code to the libs/ directory, replacing legitimate library files with weaponized versions.

Root Cause

The root cause of CVE-2021-21696 is insufficient access control enforcement in the Jenkins FilePath API implementation. The API fails to implement proper directory-level restrictions that would prevent agent processes from writing to sensitive controller directories. This represents a violation of the principle of least privilege, where agents should only have access to directories strictly necessary for their build operations.

The security model of Jenkins relies on a separation between agents (which execute potentially untrusted build code) and the controller (which manages administrative functions). This vulnerability breaks that security boundary by allowing agents to modify controller-side trusted code.

Attack Vector

The attack leverages network-accessible Jenkins installations where an attacker has gained control of an agent process. The exploitation flow involves:

1. Compromising a Jenkins agent through malicious build code, supply chain attacks, or other vulnerabilities
2. Using the FilePath APIs to enumerate and access the libs/ directory within build directories on the controller
3. Replacing legitimate shared library code with malicious code containing attacker payloads
4. Waiting for a pipeline or build job to execute the modified library code
5. Achieving unsandboxed code execution in the Jenkins controller process context

The exploitation bypasses Jenkins' Groovy sandbox protections entirely because the modified library code is treated as trusted and executed without sandbox restrictions. This grants the attacker full access to the Jenkins controller's capabilities, including accessing credentials, modifying builds, and potentially pivoting to connected systems.

Detection Methods for CVE-2021-21696

Indicators of Compromise

• Unexpected modifications to files within the libs/ directory of build workspaces
• Anomalous file write operations originating from agent processes targeting controller directories
• Unusual process behavior or network connections from the Jenkins controller process
• Modified timestamps on shared library files that don't correspond to legitimate deployments

Detection Strategies

• Monitor Jenkins audit logs for FilePath API operations targeting the libs/ directory from agent processes
• Implement file integrity monitoring on the Jenkins controller's build directories, particularly the libs/ subdirectories
• Deploy runtime application self-protection (RASP) solutions to detect unauthorized code modifications
• Use SentinelOne's Singularity platform to detect anomalous process behavior on Jenkins infrastructure

Monitoring Recommendations

• Enable comprehensive Jenkins audit logging and forward logs to a SIEM for correlation and analysis
• Configure alerts for any file modifications in trusted library directories outside of expected deployment windows
• Monitor Jenkins controller processes for unusual child process spawning or network activity
• Implement baseline behavioral analysis for Jenkins infrastructure to identify deviations

How to Mitigate CVE-2021-21696

Immediate Actions Required

• Upgrade Jenkins to version 2.319 or later (weekly) or LTS 2.303.3 or later immediately
• Review Jenkins agent configurations and restrict which agents can connect to the controller
• Audit recent builds and library modifications for signs of compromise
• Consider temporarily disabling agents from untrusted environments until patching is complete

Patch Information

Jenkins has released security patches addressing this vulnerability. Organizations should upgrade to Jenkins 2.319 or later for weekly releases, or Jenkins LTS 2.303.3 or later for Long-Term Support installations. The fix implements proper access control restrictions on the FilePath APIs to prevent agents from accessing sensitive directories on the controller.

For detailed patch information and additional security advisories, refer to the Jenkins Security Advisory #SECURITY-2423.

Workarounds

• Implement network segmentation to isolate Jenkins agents from the controller where possible
• Use the Agent-to-Controller Security subsystem to restrict which operations agents can perform on the controller
• Deploy application-level firewalls or proxies to monitor and filter FilePath API calls between agents and the controller
• Consider running agents in ephemeral, isolated containers to limit the impact of agent compromise

# Verify current Jenkins version
java -jar jenkins.war --version

# After upgrade, verify the new version is running
curl -s http://localhost:8080/api/json | grep -o '"version":"[^"]*"'