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

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

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

Q: Is CVE-2023-25722 being exploited?

CVE-2023-25722 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-25722 affect?

CVE-2023-25722 affects veracode. Severity is medium (CVSS 5.5). A credential-leak issue was discovered in related Veracode products before 2023-03-27. Veracode Scan Jenkins Plugin before 23.3.19.0, when configured for remote agent jobs, invokes the Veracode Java API Wrapper in a manner that allows local

Q: How urgent is CVE-2023-25722?

Priority 22/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

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

A credential-leak issue was discovered in related Veracode products before 2023-03-27. Veracode Scan Jenkins Plugin before 23.3.19.0, when configured for remote agent jobs, invokes the Veracode Java API Wrapper in a manner that allows local users (with OS-level access of the Jenkins remote) to discover Veracode API credentials by listing the process and its arguments. Veracode Scan Jenkins Plugin before 23.3.19.0, when configured for remote agent

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 89%)
CISA exploited list	No
Weakness	CWE-200
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-25722?

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

Is CVE-2023-25722 being exploited?

CVE-2023-25722 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-25722 affect?

CVE-2023-25722 affects veracode. Severity is medium (CVSS 5.5). A credential-leak issue was discovered in related Veracode products before 2023-03-27. Veracode Scan Jenkins Plugin before 23.3.19.0, when configured for remote agent jobs, invokes the Veracode Java API Wrapper in a manner that allows local

How urgent is CVE-2023-25722?

Priority 22/100. No elevated risk signals yet.

Software pages

Java vulnerabilities · Jenkins vulnerabilities · Jenkins plugins vulnerabilities

Related CVEs

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

References

← Back to latest CVEs