Skip to content

Jenkins AsakusaSatellite Plugin Does not Mask API Keys via Job Configuration Form

Moderate severity GitHub Reviewed Published Apr 2, 2025 to the GitHub Advisory Database • Updated Apr 2, 2025

Package

maven org.codefirst.jenkins.asakusasatellite:asakusa-satellite-plugin (Maven)

Affected versions

<= 0.1.1

Patched versions

None

Description

Jenkins AsakusaSatellite Plugin 0.1.1 and earlier stores AsakusaSatellite API keys unencrypted in job config.xml files on the Jenkins controller as part of its configuration.

These API keys 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 API keys, 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 Apr 2, 2025
Published to the GitHub Advisory Database Apr 2, 2025
Reviewed Apr 2, 2025
Last updated Apr 2, 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

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(3rd percentile)

Weaknesses

CVE ID

CVE-2025-31728

GHSA ID

GHSA-m254-f6h4-p93g

Source code

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