# CVE-2023-25722: Veracode Scan Jenkins Plugin vulnerable to information disclosure

> Local users can discover Veracode and proxy credentials by inspecting process arguments in Jenkins or Azure DevOps environments.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2023
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-fjrv-vx9m-4jpj

## What is CVE-2023-25722?

CVE-2023-25722 is a medium-severity vulnerability in n/a, published on 28 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-25722?

2 open source packages ship an affected version, including com.veracode.jenkins:veracode-scan. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.veracode.jenkins:veracode-scan` | Maven | All versions | 23.3.19.0 |
| `com.veracode.jenkins:veracode-scan` | Maven | All versions | 23.3.19.0 |

Products: Veracode Veracode.

## How do I fix CVE-2023-25722?

Upgrade com.veracode.jenkins:veracode-scan to 23.3.19.0 or later.

## Is CVE-2023-25722 being exploited?

There is no known exploitation of CVE-2023-25722 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-25721](https://insights.sbomify.com/CVE-2023-25721/): Veracode Scan Jenkins Plugin vulnerable to information disclosure (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25722 and fix it if it is affected.

What it is: CVE-2023-25722 is a medium-severity vulnerability in n/a, published on 28 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-25722 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.veracode.jenkins:veracode-scan (Maven): affected all versions; fixed in 23.3.19.0
- com.veracode.jenkins:veracode-scan (Maven): affected all versions; fixed in 23.3.19.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-25722/ (Markdown: https://insights.sbomify.com/CVE-2023-25722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-25722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-25722
- OSV: https://osv.dev/vulnerability/CVE-2023-25722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-25722/
Summaries are generated and may contain mistakes; the official description above is the record.