dbcve.org
VeracodeApplication

CVE-2023-25722

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 23.3.19.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
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 jobs and when the "Connect using proxy" option is enabled and configured with proxy credentials, allows local users of the Jenkins remote to discover proxy credentials by listing the process and its arguments. Veracode Azure DevOps Extension before 3.20.0 invokes the Veracode Java API Wrapper in a manner that allows local users (with OS-level access to the Azure DevOps Services cloud infrastructure or Azure DevOps Server) to discover Veracode API credentials by listing the process and its arguments. Veracode Azure DevOps Extension before 3.20.0, when configured with proxy credentials, allows users (with shell access to the Azure DevOps Services cloud infrastructure or Azure DevOps Server) to discover proxy credentials by listing the process and its arguments.

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 confidence

The Veracode Scan Jenkins Plugin (before 23.3.19.0) and Veracode Azure DevOps Extension (before 3.20.0) invoke the Veracode Java API Wrapper in a manner that passes credentials as command-line arguments. Local users with OS-level access can discover Veracode API credentials and proxy credentials by listing running processes and examining their arguments.

MitigationUpdate to Veracode Scan Jenkins Plugin 23.3.19.0 or later, and Veracode Azure DevOps Extension 3.20.0 or later. Additionally, rotate any credentials that may have been exposed as a precautionary measure.

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
Affected:< 23.3.19.0

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Veracode Scan Jenkins Plugin version
    Navigate to Jenkins Manage Plugins > Installed tab and locate the Veracode Scan plugin, or check the plugin's manifest file in the Jenkins plugins directory
    Affected if The installed version is earlier than 23.3.19.0
  2. Identify Veracode Azure DevOps Extension version
    Access Azure DevOps organization settings > Extensions and locate the Veracode extension, or query the extension via az extension show --name veracode-scan
    Affected if The installed version is earlier than 3.20.0
  3. Inspect running processes for credential exposure
    Use system commands such as ps auxww or Get-Process on Windows to list all running processes and examine command-line arguments for the presence of API credentials, proxy credentials, or Veracode-related secrets
    Affected if Veracode API credentials or proxy credentials appear in any process command-line arguments

A user is affected if they have a Veracode Scan Jenkins Plugin version before 23.3.19.0 or a Veracode Azure DevOps Extension version before 3.20.0, AND credentials are discoverable in running process command lines.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 23.3.19.0 or later
Fixed in 23.3.19.0
Interim mitigation

Update to Veracode Scan Jenkins Plugin 23.3.19.0 or later, and Veracode Azure DevOps Extension 3.20.0 or later. Additionally, rotate any credentials that may have been exposed as a precautionary measure.

Recommended fix High confidence

Veracode Scan Jenkins Plugin 23.3.19.0; Veracode Azure DevOps Extension 3.20.0

  1. Upgrade Veracode Scan Jenkins Plugin to version 23.3.19.0 or later via Jenkins plugin manager
  2. Upgrade Veracode Azure DevOps Extension to version 3.20.0 or later via Azure DevOps extension marketplace
  3. After upgrading, verify that credentials are no longer exposed in process arguments by reviewing the plugin/extension configuration and running process listing commands

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Veracode Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25722 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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