1. What is this vulnerability and why does it matter?
This vulnerability, identified as CVE-2024-23897, exists in the Jenkins CLI command parser. Specifically, a feature that replaces an '@' character followed by a file path in an argument with the file's contents is not properly disabled. This allows unauthenticated attackers to read arbitrary files from the Jenkins controller file system. This is a critical vulnerability because it grants unauthorized access to sensitive data, potentially including configuration files, credentials, and other confidential information stored on the Jenkins server, without requiring any authentication. The ability to read arbitrary files can lead to further compromise of the system.
2. What are the CVSS score, severity level, and disclosure details?
The CVSS score for CVE-2024-23897 is 9.8, which classifies it as a Critical severity vulnerability. The vulnerability was published on January 24, 2024, at 17:52:22 UTC and was last modified on October 21, 2025, at 23:05:25 UTC.
3. Which products, vendors, systems, and versions are affected?
The affected products and versions include:
- Jenkins 2.441 and earlier versions
- Jenkins LTS 2.426.2 and earlier versions
4. What is the technical root cause and attack vector?
The technical root cause of this vulnerability lies within the Jenkins CLI command parser. A legitimate feature designed to expand '@' followed by a file path into the contents of that file was not disabled for scenarios where it could be misused. This feature, intended perhaps for legitimate command-line argument passing, is incorrectly processed when an attacker provides a path to a sensitive file. The attack vector is through the Jenkins CLI, allowing unauthenticated attackers to supply a crafted argument containing the '@' character followed by the target file path. This vulnerability is categorized under CWE-27 (Incorrect Privilege Assignment) and CWE-22 (Path Traversal), as it allows for unauthorized file access.
5. How can this vulnerability be exploited?
This vulnerability can be exploited by an unauthenticated attacker who crafts a specific command-line argument for the Jenkins CLI. By including the '@' symbol followed by an absolute or relative path to a file on the Jenkins controller's file system, the CLI parser will automatically replace this argument with the contents of the specified file. For example, an attacker could request a command like `jenkins-cli.jar @/etc/passwd` to retrieve the contents of the `/etc/passwd` file, or `jenkins-cli.jar @/var/lib/jenkins/secrets/master.key` to access sensitive Jenkins internal files. Since no authentication is required, this makes the exploitation straightforward and highly impactful.
6. What mitigation steps and patches are available?
To mitigate this vulnerability, users should update their Jenkins instances to patched versions. Specifically, users should update to:
- Jenkins 2.442 or later (for the weekly release line)
- Jenkins LTS 2.426.3 or later (for the long-term support release line)
These updated versions disable the problematic feature in the CLI command parser, preventing unauthenticated file content disclosure.
7. How can vulnerable systems be detected?
Vulnerable systems can be detected by checking the installed version of Jenkins. Any Jenkins instance running version 2.441 or earlier (for the weekly release train) or Jenkins LTS 2.426.2 or earlier (for the long-term support release train) is susceptible to this vulnerability. System administrators should verify their Jenkins version numbers against the patched versions.
8. What are the indicators of compromise (IOCs)?
The provided CVE data does not explicitly list specific Indicators of Compromise (IOCs). However, potential IOCs could include:
- Unusual access patterns or failed login attempts on the Jenkins CLI.
- Abnormal log entries related to CLI command execution, particularly with arguments containing '@' and file paths that do not correspond to legitimate operations.
- Unexpected file access events or errors in system logs, especially for sensitive files that should not be directly accessible via the CLI.
- Presence of unauthorized data exfiltration or modification if the vulnerability was chained with other exploits.
Monitoring CLI activity and file access logs for suspicious patterns is recommended.
9. Which threat actors are known to exploit this vulnerability?
The CVE data indicates that active exploits have been published to exploit this vulnerability. While specific threat actors are not named, the public availability of exploits suggests that a wide range of malicious actors, from opportunistic attackers to more sophisticated groups, may be leveraging this flaw.
10. What public intelligence references and advisories exist?
The primary public intelligence reference is CVE-2024-23897 itself. Further details and advisories are typically released by the Jenkins project maintainers and cybersecurity organizations following the initial disclosure. Users should refer to the official Jenkins security advisories for the most up-to-date information regarding this vulnerability and recommended patching strategies.
11. What is the risk assessment and urgency level?
The risk assessment for CVE-2024-23897 is extremely high due to its CVSS score of 9.8 (Critical) and the nature of the vulnerability. It allows unauthenticated attackers to read arbitrary files from the Jenkins controller, which can expose highly sensitive information, including credentials, configuration data, and potentially source code. The existence of published active exploits further elevates the risk, indicating that the vulnerability is actively being targeted in the wild. The urgency level for patching and mitigation is therefore Critical. Organizations running affected Jenkins versions should immediately update to a patched version to prevent exploitation.