{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:gitlab-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-24397 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:gitlab-plugin to 1.9.7 or later.","what":"CVE-2025-24397 is a medium-severity vulnerability in Jenkins GitLab Plugin, published on 22 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-24397 and fix it if it is affected.\n\nWhat it is: CVE-2025-24397 is a medium-severity vulnerability in Jenkins GitLab Plugin, published on 22 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-24397 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:gitlab-plugin (Maven): affected all versions; fixed in 1.9.7\n- org.jenkins-ci.plugins:gitlab-plugin (Maven): affected all versions; fixed in 1.9.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-24397/ (Markdown: https://insights.sbomify.com/CVE-2025-24397/index.md)","id":"CVE-2025-24397","markdown":"https://insights.sbomify.com/CVE-2025-24397/index.md","name":"CVE-2025-24397","record":{"aliases":["GHSA-xhgq-h98j-859v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins GitLab Plugin","requires_auth":"low_privilege","summary":"Attackers with global configure permissions can enumerate GitLab API token and secret text credential IDs in Jenkins.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"gitlab","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Incorrect permission check in Jenkins GitLab Plugin allows enumerating credentials IDs","id":"CVE-2025-24397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Bitbucket Server Integration Plugin allows bypassing CSRF protection for any URL","id":"CVE-2025-24398"},"packages":[{"ecosystem":"Maven","fixed":["1.9.7"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-plugin","purl":null,"source":"GHSA-xhgq-h98j-859v"},{"ecosystem":"Maven","fixed":["1.9.7"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-plugin","purl":"pkg:maven/org.jenkins-ci.plugins/gitlab-plugin","source":"GHSA-xhgq-h98j-859v"}],"prev":{"headline":"Possible user enumeration","id":"CVE-2025-24391"},"products":["Jenkins GitLab Plugin"],"published":"2025-01-22","related":[{"cvss_score":8.8,"headline":"Jenkins GitLab Plugin missing permission checks","id":"CVE-2019-10301","kev_date_added":null,"published":"2019-04-18"},{"cvss_score":8,"headline":"Jenkins GitLab Plugin Cross-Site Request Forgery vulnerability","id":"CVE-2019-10300","kev_date_added":null,"published":"2019-04-18"},{"cvss_score":6.5,"headline":"Missing permission check in Jenkins GitLab Plugin","id":"CVE-2022-30955","kev_date_added":null,"published":"2022-05-17"},{"cvss_score":5.4,"headline":"Cross-site Scripting in Jenkins GitLab Plugin","id":"CVE-2022-34777","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":5.3,"headline":"Non-constant time webhook token comparison in Jenkins GitLab Plugin","id":"CVE-2022-43411","kev_date_added":null,"published":"2022-10-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-23","vendors":["Jenkins Project"]},"summary":"Attackers with global configure permissions can enumerate GitLab API token and secret text credential IDs in Jenkins.","url":"https://insights.sbomify.com/CVE-2025-24397/"}