Veracode Scan Jenkins Plugin vulnerable to information disclosure

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.4 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2023-25721: 0.65% estimated exploitation activity in the next 30 days; percentile 51.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

28 Mar 2023, 21:30 UTC

Last modified by the source

5 Apr 2023, 19:40 UTC

Source last checked

26 Oct 2026, 16:11 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c4jr-vjm4-27hq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-25721

Advisory: Veracode Scan Jenkins Plugin vulnerable to information disclosure
IDs: CVE-2023-25721, GHSA-c4jr-vjm4-27hq
Record: https://patchnext.com/advisories/cve-2023-25721 (revision 1, source checked 26 Oct 2026, 16:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.veracode.jenkins:veracode-scan 23.3.19.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.veracode.jenkins:veracode-scan: affected < 23.3.19.0; fixed in 23.3.19.0

## Suggested inspection (read-only)
- Maven com.veracode.jenkins:veracode-scan: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.veracode.jenkins:veracode-scan.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c4jr-vjm4-27hq (GitHub-reviewed advisory GHSA-c4jr-vjm4-27hq lists affected ranges: Maven com.veracode.jenkins:veracode-scan >=0 <23.3.19.0)

Commands are suggestions: review each one before running it.