Skip to content

← Public intelligence

Maven package

io.jenkins.plugins:neuvector-vulnerability-scanner

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.3MavenPublished

    Jenkins NeuVector Vulnerability Scanner Plugin missing permission check

    CVE-2023-49674 · GHSA-ph87-4x2g-6hp4

    Affected
    • Maven io.jenkins.plugins:neuvector-vulnerability-scanner < 2.2
    Fixed in
    2.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.3MavenPublished

    Jenkins NeuVector Vulnerability Scanner Plugin Cross-Site Request Forgery vulnerability

    CVE-2023-49673 · GHSA-wpfc-r5qq-7r7p

    Affected
    • Maven io.jenkins.plugins:neuvector-vulnerability-scanner < 2.2
    Fixed in
    2.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. High, CVSS 8.0MavenPublished

    Content-Security-Policy protection for user content disabled by Jenkins NeuVector Vulnerability Scanner Plugin

    CVE-2022-43434 · GHSA-wmfh-h3vm-rcxm

    Affected
    • Maven io.jenkins.plugins:neuvector-vulnerability-scanner <= 1.20
    Fixed in
    1.22· Vendor fix available
    Issue
    Jenkins sets the Content-Security-Policy header to static files served by Jenkins (specifically DirectoryBrowserSupport), such as workspaces, /userContent, or archived artifacts, unless a Resource Root URL is specified. NeuVector Vulnerability Scanner Plugin 1.20 and earlier globally disables the Content-Security-Policy header for static files served by Jenkins whenever the 'NeuVector Vulnerability Scanner' build step is executed. This allows cross-site scripting (XSS) attacks by users with the ability to control files in workspaces, archived artifacts, etc. Jenkins instances with Resource Root URL configured are unaffected.

    Recommended action: Upgrade to 1.22 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 5.5MavenPublished

    Jenkins NeuVector Vulnerability Scanner Plugin stored credentials in plain text

    CVE-2019-10430 · GHSA-3fpx-g9h3-hh8x

    Affected
    • Maven io.jenkins.plugins:neuvector-vulnerability-scanner <= 1.5
    Fixed in
    1.6· Vendor fix available
    Issue
    Jenkins NeuVector Vulnerability Scanner Plugin 1.5 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.

    Recommended action: Upgrade to 1.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →