CVE-2023-25721: Veracode Scan Jenkins Plugin before 23.3.19.0, when the "Connect using proxy" option is enabled and configured

Q: How do I fix CVE-2023-25721?

veracode: upgrade to 23.3.19.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-25721 being exploited?

CVE-2023-25721 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-25721 affect?

CVE-2023-25721 affects veracode. Severity is medium (CVSS 6.5). 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

Q: How urgent is CVE-2023-25721?

Priority 35/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

CVE-2023-25721 is a medium-severity flaw (CVSS 6.5) affecting veracode. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 49%)
CISA exploited list	No
Weakness	CWE-532
Published	2023-03-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: veracode

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-03-28 20:15 UTCPublished CVE record published
2026-06-17 05:41 UTCUpdated Record last modified

veracode veracode UPGRADE

Affected: < 23.3.19.0

Fixed in: 23.3.19.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy veracode || rpm -q veracode || veracode --version

2. UPGRADE to 23.3.19.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade veracode

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade veracode

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-25721?

veracode: upgrade to 23.3.19.0. Exact commands for each OS are on this page.

Is CVE-2023-25721 being exploited?

CVE-2023-25721 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-25721 affect?

CVE-2023-25721 affects veracode. Severity is medium (CVSS 6.5). 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

How urgent is CVE-2023-25721?

Priority 35/100. No elevated risk signals yet.

Software pages

Jenkins vulnerabilities · Jenkins plugins vulnerabilities

Related CVEs

CVE-2023-25722 MEDIUM 5.5 UPGRADE A credential-leak issue was discovered in related Veracode products before 2023-03-27

References

← Back to latest CVEs