Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:junit

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

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

  1. Medium, CVSS 5.4MavenPublished

    Cross-site Scripting in Jenkins JUnit Plugin

    CVE-2023-25761 · GHSA-ph74-8rgx-64c5

    Affected
    • Maven org.jenkins-ci.plugins:junit <= 1166.va
    Fixed in
    1166.1168.vd6b_8042a_06de· Vendor fix available
    Issue
    Jenkins JUnit Plugin 1166.va436e268e972 and earlier does not escape test case class names in JavaScript expressions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control test case class names in the JUnit resources processed by the plugin.

    Recommended action: Upgrade to 1166.1168.vd6b_8042a_06de 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 8.0MavenPublished

    Jenkins JUnit Plugin subject to Cross-site Scripting via URL conversion

    CVE-2022-45380 · GHSA-298r-5c48-7q2r

    Affected
    • Maven org.jenkins-ci.plugins:junit <= 1159.v0b
    Fixed in
    1160.vf1f01a_a_ea_b_7f· Vendor fix available
    Issue
    JUnit Plugin 1159.v0b396e1e07dd and earlier converts HTTP(S) URLs in test report output to clickable links. This is done in an unsafe manner, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission. JUnit Plugin 1160.vf1f01aaeab7f no longer converts URLs to clickable links.

    Recommended action: Upgrade to 1160.vf1f01a_a_ea_b_7f 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

    Cross-site Scripting in Jenkins JUnit Plugin

    CVE-2022-34176 · GHSA-64mj-3p92-589v

    Affected
    • Maven org.jenkins-ci.plugins:junit < 1119.1121.vc43d0fc45561
    Fixed in
    1119.1121.vc43d0fc45561· Vendor fix available
    Issue
    JUnit Plugin 1119.vaa5e9068dad7 and earlier does not escape descriptions of test results. This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Run/Update permission. JUnit Plugin 1119.1121.vc43d0fc45561 applies the configured markup formatter to descriptions of test results.

    Recommended action: Upgrade to 1119.1121.vc43d0fc45561 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. High, CVSS 8.3MavenPublished

    Improper Restriction of XML External Entity Reference in Jenkins JUnit Plugin

    CVE-2018-1000056 · GHSA-4rj6-9pjh-882r

    Affected
    • Maven org.jenkins-ci.plugins:junit <= 1.23
    Fixed in
    1.24· Vendor fix available
    Issue
    Jenkins JUnit Plugin 1.23 and earlier processes XML external entities in files it parses as part of the build process, allowing attackers with user permissions in Jenkins to extract secrets from the Jenkins master, perform server-side request forgery, or denial-of-service attacks.

    Recommended action: Upgrade to 1.24 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 →
  5. Medium, CVSS 6.5MavenPublished

    Jenkins JUnit Plugin CSRF vulnerability

    CVE-2018-1000411 · GHSA-x9gm-m8pp-54vx

    Affected
    • Maven org.jenkins-ci.plugins:junit <= 1.25
    Fixed in
    1.26· Vendor fix available
    Issue
    A cross-site request forgery vulnerability exists in Jenkins JUnit Plugin 1.25 and earlier in TestObject.java that allows setting the description of a test result.

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