CVE-2025-24397: Medium severity jenkins gitlab vulnerability
An incorrect permission check in Jenkins GitLab Plugin 1.9.6 and earlier allows attackers with global Item/Configure permission (while lacking Item/Configure permission on any particular job) to enumerate credential IDs of GitLab API token and Secret text credentials stored in Jenkins.
Other sources
The Jenkins GitLab Plugin 1.9.6 and earlier does not correctly perform a permission check in an HTTP endpoint.
This allows attackers with global Item/Configure permission (while lacking Item/Configure permission on any particular job) to enumerate credential IDs of GitLab API token credentials and Secret text credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability.
An enumeration of credential IDs in GitLab Plugin 1.9.7 requires Overall/Administer permission.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-24397?
CVE-2025-24397 has a medium severity rating due to its potential to leak sensitive credential IDs.
How do I fix CVE-2025-24397?
To fix CVE-2025-24397, upgrade the Jenkins GitLab Plugin to version 1.9.7 or later.
What versions are affected by CVE-2025-24397?
CVE-2025-24397 affects Jenkins GitLab Plugin versions 1.9.6 and earlier.
Who can exploit CVE-2025-24397?
Attackers with global Item/Configure permission can exploit CVE-2025-24397 to enumerate credential IDs.
What types of credentials are exposed in CVE-2025-24397?
CVE-2025-24397 exposes GitLab API token and Secret text credentials stored in Jenkins.