Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:nunit

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

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

  1. Medium, CVSS 5.3MavenPublished

    Jenkins NUnit Plugin vulnerable to Protection Mechanism Failure

    CVE-2022-43414 · GHSA-8cxw-wvhc-p4x4

    Affected
    • Maven org.jenkins-ci.plugins:nunit <= 0.27
    Fixed in
    0.28· Vendor fix available
    Issue
    Jenkins NUnit Plugin 0.27 and earlier implements an agent-to-controller message that parses files inside a user-specified directory as test results, allowing attackers able to control agent processes to obtain test results from files in an attacker-specified directory on the Jenkins controller. NUnit Plugin 0.28 changes the message type from agent-to-controller to controller-to-agent, preventing execution on the controller.

    Recommended action: Upgrade to 0.28 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. High, CVSS 7.6MavenPublished

    XXE vulnerability in NUnit Plugin

    CVE-2020-2115 · GHSA-xvhf-q744-5xm8

    Affected
    • Maven org.jenkins-ci.plugins:nunit < 0.26
    Fixed in
    0.26· Vendor fix available
    Issue
    NUnit Plugin 0.25 and earlier does not configure the XML parser to prevent XML external entity (XXE) attacks. This allows a user able to control the input files for its post-build step to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller, server-side request forgery, or denial-of-service attacks. NUnit Plugin 0.26 disables external entity processing for its XML parser.

    Recommended action: Upgrade to 0.26 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 →