{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:gradle. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39152 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:gradle to 2.8.1 or later.","what":"CVE-2023-39152 is a medium-severity vulnerability in Jenkins Gradle Plugin, published on 26 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-39152 and fix it if it is affected.\n\nWhat it is: CVE-2023-39152 is a medium-severity vulnerability in Jenkins Gradle Plugin, published on 26 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-39152 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:gradle (Maven): affected all versions; fixed in 2.8.1\n- org.jenkins-ci.plugins:gradle (Maven): affected all versions; fixed in 2.8.1\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-2023-39152/ (Markdown: https://insights.sbomify.com/CVE-2023-39152/index.md)","id":"CVE-2023-39152","markdown":"https://insights.sbomify.com/CVE-2023-39152/index.md","name":"CVE-2023-39152","record":{"aliases":["GHSA-pvjf-4hfg-wr84"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Gradle Plugin","requires_auth":"low_privilege","summary":"Attackers can view unmasked credentials in build logs due to incorrect control flow in the Jenkins Gradle Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"gradle","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"Always-incorrect control flow implementation in Jenkins Gradle Plugin 2.8 may result in credentials not being masked (i.e., replaced with asterisks) in the build log in some circumstances.","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 control flow in Jenkins Gradle Plugin breaks credentials masking in the build log","id":"CVE-2023-39152","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"CSRF vulnerability in GitLab Authentication Plugin","id":"CVE-2023-39153"},"packages":[{"ecosystem":"Maven","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gradle","purl":null,"source":"GHSA-pvjf-4hfg-wr84"},{"ecosystem":"Maven","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gradle","purl":"pkg:maven/org.jenkins-ci.plugins/gradle","source":"GHSA-pvjf-4hfg-wr84"}],"prev":{"headline":"Jenkins Stored Cross-site Scripting vulnerability","id":"CVE-2023-39151"},"products":["Jenkins Gradle Plugin"],"published":"2023-07-26","related":[],"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":"2024-10-23","vendors":["Jenkins Project"]},"summary":"Attackers can view unmasked credentials in build logs due to incorrect control flow in the Jenkins Gradle Plugin.","url":"https://insights.sbomify.com/CVE-2023-39152/"}