CVE-2025-31728: Medium severity jenkins vulnerability
Jenkins AsakusaSatellite Plugin 0.1.1 and earlier does not mask AsakusaSatellite API keys displayed on the job configuration form, increasing the potential for attackers to observe and capture them.
Other sources
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.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-31728?
CVE-2025-31728 is considered a medium severity vulnerability due to the risk of API key exposure.
How do I fix CVE-2025-31728?
To fix CVE-2025-31728, upgrade the Jenkins AsakusaSatellite Plugin to version 0.1.2 or later.
What are the potential impacts of CVE-2025-31728?
The potential impacts of CVE-2025-31728 include unauthorized access to the AsakusaSatellite API if API keys are compromised.
Who is affected by CVE-2025-31728?
Users of Jenkins AsakusaSatellite Plugin version 0.1.1 and earlier are affected by CVE-2025-31728.
Is there a workaround for CVE-2025-31728?
Currently, there are no known workarounds for CVE-2025-31728 aside from upgrading the plugin.