# CVE-2023-49673: Jenkins NeuVector Vulnerability Scanner Plugin Cross-Site Request Forgery vulnerability

> Attackers can force Jenkins users to connect to malicious servers via CSRF in the NeuVector Vulnerability Scanner Plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Nov 2023
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-wpfc-r5qq-7r7p

## What is CVE-2023-49673?

CVE-2023-49673 is a high-severity vulnerability in Jenkins NeuVector Vulnerability Scanner Plugin, published on 29 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A cross-site request forgery (CSRF) vulnerability in Jenkins NeuVector Vulnerability Scanner Plugin 1.22 and earlier allows attackers to connect to an attacker-specified hostname and port using attacker-specified username and password.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

2 open source packages ship an affected version, including io.jenkins.plugins:neuvector-vulnerability-scanner. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:neuvector-vulnerability-scanner` | Maven | All versions | 2.2 |
| `io.jenkins.plugins:neuvector-vulnerability-scanner` | Maven | All versions | 2.2 |

Products: Jenkins Google Compute Engine, Jenkins Jira, Jenkins Matlab, Jenkins Neuvector Vulnerability Scanner.

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

Upgrade io.jenkins.plugins:neuvector-vulnerability-scanner to 2.2 or later.

## Is CVE-2023-49673 being exploited?

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

## Other vulnerabilities in Jenkins NeuVector Vulnerability Scanner Plugin

- [CVE-2019-16548](https://insights.sbomify.com/CVE-2019-16548/): Jenkins Google Compute Engine Plugin Cross-Site Request Forgery vulnerability (high 8.8)
- [CVE-2019-16546](https://insights.sbomify.com/CVE-2019-16546/): Jenkins Google Compute Engine Plugin does not verify SSH host keys when connecting agents created by the plugin (medium 5.9)
- [CVE-2022-29052](https://insights.sbomify.com/CVE-2022-29052/): Private key stored in plain text by Jenkins Google Compute Engine Plugin (medium 4.3)
- [CVE-2019-16547](https://insights.sbomify.com/CVE-2019-16547/): Jenkins Google Compute Engine Plugin Missing Authorization vulnerability (medium 4.3)
- [CVE-2023-49652](https://insights.sbomify.com/CVE-2023-49652/): Jenkins Google Compute Engine Plugin has incorrect permission checks (low 2.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49673 is a high-severity vulnerability in Jenkins NeuVector Vulnerability Scanner Plugin, published on 29 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-49673 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:neuvector-vulnerability-scanner (Maven): affected all versions; fixed in 2.2
- io.jenkins.plugins:neuvector-vulnerability-scanner (Maven): affected all versions; fixed in 2.2

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-49673/ (Markdown: https://insights.sbomify.com/CVE-2023-49673/index.md)
```

## Sources

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

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