Jenkins Command Line Interface (CLI): file access flaw under attack

What is affected

Jenkins Command Line Interface (CLI) is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

Jenkins Command Line Interface (CLI) contains a path traversal vulnerability that allows attackers limited read access to certain files, which can lead to code execution.

What an attacker can do

This is a file access flaw. It lets an attacker read or write files they should never reach, such as configuration files that hold passwords, or upload a malicious file that the system then runs.

How it is reached

Over the internet or network

Access the attacker needs

No account needed

Does the victim have to do something?

No, works without the victim doing anything

CISA records this vulnerability as known to be used in ransomware campaigns: attackers use it to get in, then encrypt files and demand payment.

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer Jenkins Command Line Interface (CLI) at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Vendor advisories and fixes

• jenkins.iowww.jenkins.io/security/advisory/2024-01-24/#SECURITY-3314

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on August 19, 2024, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by September 9, 2024, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 100% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 100.0% of all scored vulnerabilities.

Its CVSS severity score is 9.8 out of 10 (critical), as recorded in the US National Vulnerability Database.

Technical description

Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read arbitrary files on the Jenkins controller file system.