# Veracode Scan Jenkins Plugin vulnerable to information disclosure

Advisory record · `GHSA-fjrv-vx9m-4jpj`

- **Identifiers:** `GHSA-fjrv-vx9m-4jpj` · `CVE-2023-25722`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-214](https://cwe.mitre.org/data/definitions/214.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-214](https://agentprime.io/advisories/tag/cwe-214.md)
- **Published:** 28 Mar 2023
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Mar 2023, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.veracode.jenkins:veracode-scan` (Maven): affected `<23.3.19.0`; fixed in `23.3.19.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 10th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 28 Mar 2023. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-fjrv-vx9m-4jpj](https://github.com/advisories/GHSA-fjrv-vx9m-4jpj)
- [OSV: GHSA-fjrv-vx9m-4jpj](https://osv.dev/vulnerability/GHSA-fjrv-vx9m-4jpj)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-25722>
- <https://community.veracode.com/s/global-search/CVE-2023-25722>
- <https://docs.veracode.com/updates/r/c_all_int#veracode-jenkins-plugin-233190>
- <https://github.com/jenkinsci/veracode-scan-plugin>
- <https://veracode.com/>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fjrv-vx9m-4jpj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fjrv-vx9m-4jpj/>. Everything for agents: <https://agentprime.io/llms.txt>.