Controller file replacement via unvalidated agent message
Published Nov 12, 2021 · Updated Aug 4, 2024
Agent-to-controller validation failure in Jenkins Squash TM Publisher Plugin 1.0.0 and earlier allows attackers to replace controller files. The message handler accepts its input without validation and uses it to select a controller-side file and replace that file with an attacker-controlled JSON string. Exploitation requires control of a connected Jenkins agent process and can corrupt writable controller data, causing integrity and availability loss.
Summary
What happened
Agent-to-controller validation failure in Jenkins Squash TM Publisher Plugin 1.0.0 and earlier allows attackers to replace controller files. The message handler accepts its input without validation and uses it to select a controller-side file and replace that file with an attacker-controlled JSON string. Exploitation requires control of a connected Jenkins agent process and can corrupt writable controller data, causing integrity and availability loss.
The record
- CVE
- CVE-2021-43578
- Published
- Nov 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Squash TM Publisher (Squash4Jenkins) Plugin
- Classifications
- CWE-693, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=1.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo