CVE-2021-21611: XSS

Published Jan 13, 2021
·
Updated

A flaw was found in jenkins. A cross-site scripting (XSS) vulnerability is possible due to display names and IDs of item types shown on the New Item page not being properly escaped. The highest threat from this vulnerability is to data confidentiality and integrity.

Other sources

Jenkins 2.274 and earlier, LTS 2.263.1 and earlier does not escape display names and IDs of item types shown on the New Item page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to specify display names or IDs of item types.

Jenkins 2.274 and earlier, LTS 2.263.1 and earlier does not escape display names and IDs of item types shown on the New Item page.

This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to specify display names or IDs of item types.

As of the publication of this advisory, the Jenkins security team is not aware of any plugins published via the Jenkins project update center that allow doing this. Jenkins 2.275, LTS 2.263.2 escapes display names and IDs of item types shown on the New Item page.

Affected Software

15 affected componentsFixes available
redhat/jenkins<0:2.263.3.1612433584-1.el7
0:2.263.3.1612433584-1.el7
redhat/conmon<2:2.0.21-1.rhaos4.5.el8
2:2.0.21-1.rhaos4.5.el8
redhat/jenkins<0:2.263.3.1612434332-1.el7
0:2.263.3.1612434332-1.el7
redhat/machine-config-daemon<0:4.5.0-202102050524.p0.git.2594.ff3b8c0.el8
0:4.5.0-202102050524.p0.git.2594.ff3b8c0.el8
redhat/openshift<0:4.5.0-202102050524.p0.git.0.9229406.el8
0:4.5.0-202102050524.p0.git.0.9229406.el8
redhat/openshift-ansible<0:4.5.0-202102031005.p0.git.0.c6839a2.el7
0:4.5.0-202102031005.p0.git.0.c6839a2.el7
redhat/openshift-clients<0:4.5.0-202102051529.p0.git.3612.61b096a.el7
0:4.5.0-202102051529.p0.git.3612.61b096a.el7
redhat/runc<0:1.0.0-72.rhaos4.5.giteadfc6b.el8
0:1.0.0-72.rhaos4.5.giteadfc6b.el8
redhat/jenkins<0:2.263.3.1612434510-1.el8
0:2.263.3.1612434510-1.el8
maven/org.jenkins-ci.main:jenkins-core>=2.264<=2.274
2.275
maven/org.jenkins-ci.main:jenkins-core<=2.263.1
2.263.2
redhat/jenkins<2.275
2.275
redhat/jenkins LTS<2.263.2
2.263.2
Jenkins Jenkins<=2.263.1
Jenkins Jenkins<=2.274

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jenkins to a version that resolves this vulnerability.

    Fixed in 0:2.263.3.1612433584-1.el7
  2. Upgrade

    Upgrade redhat/conmon to a version that resolves this vulnerability.

    Fixed in 2:2.0.21-1.rhaos4.5.el8
  3. Upgrade

    Upgrade redhat/jenkins to a version that resolves this vulnerability.

    Fixed in 0:2.263.3.1612434332-1.el7
  4. Upgrade

    Upgrade redhat/machine-config-daemon to a version that resolves this vulnerability.

    Fixed in 0:4.5.0-202102050524.p0.git.2594.ff3b8c0.el8
  5. Upgrade

    Upgrade redhat/openshift to a version that resolves this vulnerability.

    Fixed in 0:4.5.0-202102050524.p0.git.0.9229406.el8
  6. Upgrade

    Upgrade redhat/openshift-ansible to a version that resolves this vulnerability.

    Fixed in 0:4.5.0-202102031005.p0.git.0.c6839a2.el7
  7. Upgrade

    Upgrade redhat/openshift-clients to a version that resolves this vulnerability.

    Fixed in 0:4.5.0-202102051529.p0.git.3612.61b096a.el7
  8. Upgrade

    Upgrade redhat/runc to a version that resolves this vulnerability.

    Fixed in 0:1.0.0-72.rhaos4.5.giteadfc6b.el8
  9. Upgrade

    Upgrade redhat/jenkins to a version that resolves this vulnerability.

    Fixed in 0:2.263.3.1612434510-1.el8
  10. Upgrade

    Upgrade maven/org.jenkins-ci.main:jenkins-core to a version that resolves this vulnerability.

    Fixed in 2.275
  11. Upgrade

    Upgrade maven/org.jenkins-ci.main:jenkins-core to a version that resolves this vulnerability.

    Fixed in 2.263.2
  12. Upgrade

    Upgrade redhat/jenkins to a version that resolves this vulnerability.

    Fixed in 2.275
  13. Upgrade

    Upgrade redhat/jenkins LTS to a version that resolves this vulnerability.

    Fixed in 2.263.2
  14. Upgrade

    Upgrade Jenkins to a version that resolves this vulnerability.

    Fixed in 2.275
  15. Upgrade

    Upgrade Jenkins (LTS) to a version that resolves this vulnerability.

    Fixed in 2.263.2

Event History

Jan 13, 2021
CVE Published
12:00 AM
CVE Published
via MITRE·03:55 PM
Data Sourced
via MITRE·03:55 PM
Description
Feb 4, 2021
Data Sourced
via Red Hat·01:50 PM
DescriptionSeverityAffected Software
May 24, 2022
Advisory Published
05:39 PM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2021-21611?

The severity of CVE-2021-21611 is high.

2

How does CVE-2021-21611 affect Jenkins?

CVE-2021-21611 affects Jenkins versions 2.274 and earlier, LTS 2.263.1 and earlier.

3

What is the vulnerability in CVE-2021-21611?

CVE-2021-21611 is a cross-site scripting (XSS) vulnerability in Jenkins.

4

How can an attacker exploit CVE-2021-21611?

An attacker can exploit CVE-2021-21611 by specifying display names or IDs of item types on the New Item page.

5

How can I fix CVE-2021-21611?

To fix CVE-2021-21611, update Jenkins to version 2.275 or 2.263.2 and apply the necessary patches.

Company

Resources

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