Skip to content

← Public intelligence

Maven package

org.jenkins-ci.plugins:token-macro

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. High, CVSS 7.5MavenPublished

    Improper Restriction of XML External Entity Reference Jenkins Token Macro Plugin

    CVE-2019-10337 · GHSA-g6h2-4x64-c59x

    Affected
    • Maven org.jenkins-ci.plugins:token-macro <= 2.7
    Fixed in
    2.8· Vendor fix available
    Issue
    An XML external entities (XXE) vulnerability in Jenkins Token Macro Plugin 2.7 and earlier allowed attackers able to control a the content of the input file for the "XML" macro to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks.

    Recommended action: Upgrade to 2.8 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 6.5MavenPublished

    Jenkins Token Macro Plugin's recursive token expansion results in information disclosure and DoS

    CVE-2019-1003011 · GHSA-23h9-m55m-c5jp

    Affected
    • Maven org.jenkins-ci.plugins:token-macro <= 2.5
    Fixed in
    2.6· Vendor fix available
    Issue
    Jenkins Token Macro Plugin recursively applied token expansion. This could be used by users able to affect input to token expansion (such as change log messages), to inject additional tokens into the input, which would then be expanded, resulting in information disclosure (for example values of environment variables), or denial of service. Most tokens have been changed to no longer recursively apply token expansion.

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