dbcve.org
Token MacroApplication · Jenkins

CVE-2019-1003011

HIGH · 8.1 CVSS v3.1 Published 2019-02-06
Fix available
A fix is available. Upgrade to after 2.5 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An information exposure and denial of service vulnerability exists in Jenkins Token Macro Plugin 2.5 and earlier in src/main/java/org/jenkinsci/plugins/tokenmacro/Parser.java, src/main/java/org/jenkinsci/plugins/tokenmacro/TokenMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/AbstractChangesSinceMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/ChangesSinceLastBuildMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/ProjectUrlMacro.java that allows attackers with the ability to control token macro input (such as SCM changelogs) to define recursive input that results in unexpected macro evaluation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins Token Macro Plugin before 2.6 has a denial-of-service vulnerability where recursive macro input causes infinite evaluation loops. Attackers with control over token macro input (e.g., SCM changelogs) can define malicious recursive input that leads to unexpected macro evaluation, potentially causing the Jenkins instance to become unresponsive or expose sensitive information through error messages.

MitigationUpgrade Jenkins Token Macro Plugin to version 2.6 or later, which includes fixes for recursion detection and input validation. If upgrade is not immediately possible, restrict permissions for users who can modify token macro inputs such as SCM changelogs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Token MacroApplication
Affected:<= 2.5
Openshift Container PlatformApplication
Affected:= 3.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Jenkins Token Macro Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate the Token Macro Plugin, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins token-macro
    Affected if The installed version is 2.5 or earlier (versions <= 2.5 are affected)
  2. Verify plugin is present in Jenkins
    Confirm the Token Macro plugin is installed by checking Manage Jenkins > Manage Plugins > Installed, or via API: /api/json?tree=plugins[shortName,version]
    Affected if The plugin is installed and the version cannot be determined or is confirmed to be <= 2.5
  3. Identify use of token macros with SCM input
    Review Jenkins jobs and configurations that use token macros in SCM-related fields such as changelog templates, commit messages, or branch specifications. Check job configurations for references to token macros like ${CHANGES}, ${SVN_REVISION}, or custom macro usage.
    Affected if Jobs or configurations use token macros where input can be controlled by users with SCM commit access (e.g., commit messages, changelog text)
  4. Check for macro definitions in Jenkins configuration
    Inspect Jenkins configuration files (config.xml) and any managed files for custom macro definitions that could contain recursive references. Look for <tokenMacro> elements in job or system configuration.
    Affected if Custom token macro definitions exist that could potentially contain recursive or self-referential patterns

You are affected if Jenkins Token Macro Plugin version is 2.5 or earlier AND your Jenkins jobs use token macros with SCM or user-controlled input that could be crafted into recursive macro evaluations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.5
Interim mitigation

Upgrade Jenkins Token Macro Plugin to version 2.6 or later, which includes fixes for recursion detection and input validation. If upgrade is not immediately possible, restrict permissions for users who can modify token macro inputs such as SCM changelogs.

Fix this in Token Macro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003011 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1003011 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data