CVE-2023-49674 — neuvector-vulnerability-s…
MEDIUMCVE-2023-49674 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in io.jenkins.plugins:neuvector-vulnerability-scanner. A fix is available for io.jenkins.plugins:neuvector-vulnerability-scanner — see the affected versions and patch details below.
Jenkins NeuVector Vulnerability Scanner Plugin missing permission check
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.jenkins.plugins:neuvector-vulnerability-scannerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins NeuVector Vulnerability Scanner Plugin 1.22 and earlier does not perform a permission check in a connection test HTTP endpoint. This allows attackers with Overall/Read permission to connect to an attacker-specified hostname and port using attacker-specified username and password. Additionally, this HTTP endpoint does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
NeuVector Vulnerability Scanner Plugin 2.2 requires POST requests and Overall/Administer permission for the affected HTTP endpoint.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:neuvector-vulnerability-scanner | all versions | 2.2io.jenkins.plugins:neuvector-vulnerability-scanner:2.2 |
Affected Products
neuvector vulnerability scannerjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:neuvector-vulnerability-scanner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:neuvector-vulnerability-scanner to 2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49674 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2023-49674 in your dependencies?
Find it across Maven, including transitive dependencies.