CVE-2025-64144: Medium severity Jenkins ByteGuard Build Actions Plugin vulnerability
Jenkins ByteGuard Build Actions Plugin 1.0 and earlier stores API tokens unencrypted in job config.xml files on the Jenkins controller as part of its configuration.
These tokens can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Additionally, the job configuration form does not mask these credentials, increasing the potential for attackers to observe and capture them.
As of publication of this advisory, there is no fix.
Other sources
Jenkins ByteGuard Build Actions Plugin 1.0 stores API tokens unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission, or access to the Jenkins controller file system.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-64144?
CVE-2025-64144 has a high severity rating due to the exposure of sensitive API tokens.
How do I fix CVE-2025-64144?
To fix CVE-2025-64144, ensure that sensitive API tokens are encrypted in job config.xml files and restrict access permissions appropriately.
What are the potential risks associated with CVE-2025-64144?
The risks include unauthorized access to Jenkins jobs and potential exploitation of API tokens by malicious users.
Who is affected by CVE-2025-64144?
Any Jenkins installation using the ByteGuard Build Actions Plugin version 1.0 is affected by CVE-2025-64144.
Can CVE-2025-64144 lead to data breaches?
Yes, due to the exposure of unencrypted API tokens, CVE-2025-64144 can potentially lead to data breaches if exploited.