Skip to content

Jenkins ByteGuard Build Actions Plugin does not mask API tokens displayed on the job configuration form

Moderate severity GitHub Reviewed Published Oct 29, 2025 to the GitHub Advisory Database • Updated Oct 29, 2025

Package

maven io.jenkins.plugins:byteguard-build-actions (Maven)

Affected versions

<= 1.0

Patched versions

None

Description

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.

References

Published by the National Vulnerability Database Oct 29, 2025
Published to the GitHub Advisory Database Oct 29, 2025
Reviewed Oct 29, 2025
Last updated Oct 29, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

Weaknesses

Missing Encryption of Sensitive Data

The product does not encrypt sensitive or critical information before storage or transmission. Learn more on MITRE.

CVE ID

CVE-2025-64145

GHSA ID

GHSA-vmm2-53rc-43v3

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.