CVE-2019-1003011: Infoleak

Published Feb 6, 2019
·
Updated

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.

Other sources

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.

Affected Software

3 affected componentsFixes available
maven/org.jenkins-ci.plugins:token-macro<=2.5
2.6
Jenkins Token Macro Jenkins<=2.5
redhat OpenShift Container Platform=3.11

Event History

Feb 6, 2019
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
May 13, 2022
Advisory Published
01:15 AM

Frequently Asked Questions

1

What is the severity of CVE-2019-1003011?

CVE-2019-1003011 is classified as an information exposure and denial of service vulnerability.

2

How do I fix CVE-2019-1003011?

To fix CVE-2019-1003011, upgrade the Jenkins Token Macro Plugin to version 2.6 or later.

3

What products are affected by CVE-2019-1003011?

CVE-2019-1003011 affects Jenkins Token Macro Plugin version 2.5 and earlier, as well as Red Hat OpenShift Container Platform version 3.11.

4

What types of vulnerabilities does CVE-2019-1003011 include?

CVE-2019-1003011 includes both information exposure and denial of service vulnerabilities.

5

Is there a workaround for CVE-2019-1003011?

There are no known workarounds for CVE-2019-1003011; the best action is to upgrade the affected software.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203