CVE-2023-25721 — veracode-scan
MEDIUMCVE-2023-25721 is a medium-severity (CVSS 4.4) CWE-532 vulnerability in com.veracode.jenkins:veracode-scan. A fix is available for com.veracode.jenkins:veracode-scan — see the affected versions and patch details below.
Veracode Scan Jenkins Plugin vulnerable to information disclosure
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-25721.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.veracode.jenkins:veracode-scanReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Veracode Scan Jenkins Plugin before 23.3.19.0 is vulnerable to information disclosure of proxy credentials in job logs under specific configurations.
Users are potentially affected if they:
- are using Veracode Scan Jenkins Plugin prior to 23.3.19.0
- AND have configured Veracode Scan to run on remote agent jobs
- AND have enabled the "Connect using proxy" option
- AND have configured the proxy settings with proxy credentials
- AND a Jenkins admin has enabled debug in global system settings.
By default, even in this configuration only the job owner or Jenkins admin can view the job log.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.veracode.jenkins:veracode-scan | all versions | 23.3.19.0com.veracode.jenkins:veracode-scan:23.3.19.0 |
Affected Products
veracodeveracodeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.veracode.jenkins:veracode-scan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.veracode.jenkins:veracode-scan to 23.3.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-25721 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2023-25721 in your dependencies?
Find it across Maven, including transitive dependencies.