VeracodeApplication
CVE-2023-25721
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVeracode 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Veracode Scan Jenkins Plugin before version 23.3.19.0 exposes proxy credentials in job logs when three conditions coincide: the 'Connect using proxy' option is enabled with proxy credentials configured, Jenkins global debug mode is enabled, and a scan is configured for remote agent jobs. Any user with permission to view job logs can discover these credentials through log output.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
VeracodeApplication
< 23.3.19.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Veracode Scan Jenkins Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Veracode Scan' or 'Veracode' to find the installed version. Alternatively, check the plugin's manifest file (META-INF/MANIFEST.MF) in the plugin's directory on the Jenkins controller.Affected if The plugin version is present and is lower than 23.3.19.0, or the plugin is installed but the version cannot be determined (assume vulnerable if other conditions apply).
-
Check for proxy configuration in job settingsReview your Jenkins jobs that use the Veracode Scan plugin. In each job's configuration, look for the 'Connect using proxy' option in the Veracode Scan build step. Check if proxy credentials (username/password) are configured in the proxy settings.Affected if The 'Connect using proxy' option is enabled AND proxy credentials are configured in any Veracode Scan job configuration.
-
Confirm Jenkins global debug mode is enabledNavigate to Manage Jenkins > System Log > and check for debug-level logging. Also check the Jenkins startup script (jenkins.xml or jenkins.conf) for the '--debug' flag, or check Manage Jenkins > System Configuration for debug settings. Additionally, look for 'DEBUG' level loggers in the log recorder configurations.Affected if Jenkins global debug mode is enabled at the system level (not just per-job logging).
-
Identify Veracode scans configured for remote agent jobsReview your Veracode Scan job configurations. In each job using the Veracode Scan plugin, check if 'Run on remote agent' or equivalent remote execution option is selected, or check if the job is tied to a specific agent/agent label for execution.Affected if Any Veracode Scan job is configured to run on a remote agent (distributed build) rather than only on the controller.
-
Inspect recent job logs for credential exposureNavigate to the build history of Veracode Scan jobs that meet the above conditions. Open recent build logs and search for patterns indicating proxy credentials (look for strings containing proxy host, port, and any visible username/password values in DEBUG log sections).Affected if Job logs contain proxy credentials, proxy username, proxy password, or similar sensitive proxy authentication data visible in the output.
A user is affected if they have Veracode Scan Jenkins Plugin version < 23.3.19.0 AND all three conditions are present: proxy credentials configured with 'Connect using proxy' enabled, Jenkins global debug mode is on, and Veracode scans are running on remote agent jobs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.3.19.0
Upgrade to Veracode Scan Jenkins Plugin version 23.3.19.0 or later. Additionally, review job logs for any credential exposure, disable Jenkins debug mode if not required for troubleshooting, and rotate any proxy credentials that may have been disclosed.
23.3.19.0
- Log in to Jenkins as an administrator
- Navigate to Manage Jenkins > Manage Plugins
- Click on the 'Installed' tab
- Locate the 'Veracode Scan' plugin in the list
- If an update is available, click 'Update' to upgrade to version 23.3.19.0 or later
- After the update completes, restart Jenkins to apply the changes
- Verify the plugin version is 23.3.19.0 or higher under Manage Plugins > Installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Veracode
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25721 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25721 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data