{"answers":{"affected":"2 open source packages ship an affected version, including com.veracode.jenkins:veracode-scan. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25721 in the wild and no public exploit code.","fix":"Upgrade com.veracode.jenkins:veracode-scan to 23.3.19.0 or later.","what":"CVE-2023-25721 is a medium-severity vulnerability in n/a, published on 28 Mar 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-25721 and fix it if it is affected.\n\nWhat it is: CVE-2023-25721 is a medium-severity vulnerability in n/a, published on 28 Mar 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-25721 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.veracode.jenkins:veracode-scan (Maven): affected all versions; fixed in 23.3.19.0\n- com.veracode.jenkins:veracode-scan (Maven): affected all versions; fixed in 23.3.19.0\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-25721/ (Markdown: https://insights.sbomify.com/CVE-2023-25721/index.md)","id":"CVE-2023-25721","markdown":"https://insights.sbomify.com/CVE-2023-25721/index.md","name":"CVE-2023-25721","record":{"aliases":["GHSA-c4jr-vjm4-27hq"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Users with job log access can discover proxy credentials when specific debug and proxy settings are enabled in the Veracode Scan Jenkins Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"veracode","vendor":"veracode"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","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-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Veracode Scan Jenkins Plugin before 23.3.19.0, when the \"Connect using proxy\" option is enabled and configured with proxy credentials and when the Jenkins global system setting debug is enabled and when a scan is configured for remote agent jobs, allows users (with access to view the job log) to discover proxy credentials.","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":"Veracode Scan Jenkins Plugin vulnerable to information disclosure","id":"CVE-2023-25721","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":"Veracode Scan Jenkins Plugin vulnerable to information disclosure","id":"CVE-2023-25722"},"packages":[{"ecosystem":"Maven","fixed":["23.3.19.0"],"introduced":["0"],"last_affected":[],"package":"com.veracode.jenkins:veracode-scan","purl":null,"source":"GHSA-c4jr-vjm4-27hq"},{"ecosystem":"Maven","fixed":["23.3.19.0"],"introduced":["0"],"last_affected":[],"package":"com.veracode.jenkins:veracode-scan","purl":"pkg:maven/com.veracode.jenkins/veracode-scan","source":"GHSA-c4jr-vjm4-27hq"}],"prev":{"headline":"Code injection in n/a","id":"CVE-2023-25719"},"products":["n/a"],"published":"2023-03-28","related":[{"cvss_score":5.5,"headline":"Veracode Scan Jenkins Plugin vulnerable to information disclosure","id":"CVE-2023-25722","kev_date_added":null,"published":"2023-03-28"}],"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-02-19","vendors":["n/a"]},"summary":"Users with job log access can discover proxy credentials when specific debug and proxy settings are enabled in the Veracode Scan Jenkins Plugin.","url":"https://insights.sbomify.com/CVE-2023-25721/"}