CVE-2024-43044
Published: 07 August 2024
Summary
CVE-2024-43044 is a high-severity Improper Check for Unusual or Exceptional Conditions (CWE-754) vulnerability in Jenkins Jenkins. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 1.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Jenkins 2.470 and earlier, along with LTS 2.452.3 and earlier, contain a vulnerability in the Remoting library that permits agent processes to invoke the ClassLoaderProxy#fetchJar method and thereby read arbitrary files from the Jenkins controller file system. The flaw is tracked as CVE-2024-43044 and carries a CVSS 3.1 base score of 8.8.
An attacker who can run or control a Jenkins agent process can exploit the issue over the network with low attack complexity and without user interaction. Successful exploitation grants the agent read access to any file on the controller, resulting in high impact to confidentiality, integrity, and availability.
The Jenkins security advisory published on 7 August 2024 at https://www.jenkins.io/security/advisory/2024-08-07/#SECURITY-3430 addresses the issue. The associated EPSS score has remained at 0.6590 from disclosure through the present measurement, indicating steady but not sharply increasing exploitation interest.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2593
Vulnerability details
Jenkins 2.470 and earlier, LTS 2.452.3 and earlier allows agent processes to read arbitrary files from the Jenkins controller file system by using the `ClassLoaderProxy#fetchJar` method in the Remoting library.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires detection and response to audit logging failures as an unusual or exceptional condition.
Implements detection of unusual or exceptional conditions followed by safe mode entry, reducing the window for exploitation of unchecked conditions.
Training ensures users perform required checks for unusual or exceptional conditions as part of contingency roles, limiting attacker leverage from skipped validations.
IR testing directly validates checks for unusual or exceptional conditions that could indicate security incidents.
Requires ongoing monitoring of organization-defined metrics and analysis, enabling checks for unusual or exceptional conditions.
Security testing routinely checks for unusual or exceptional inputs/conditions, identifying missing validation steps that flaw remediation then resolves.
Requires detection of unusual conditions followed by a controlled transition to the defined failure state.
MTTF determination forces explicit checks for conditions that precede predictable component failure.