CVE-2021-21604: High severity Jenkins Jenkins vulnerability

Published Jan 13, 2021
·
Updated

A flaw was found in jenkins. An attacker with permission to create or configure various objects to inject crafted content into Old Data Monitor can cause the instantiation of potentially unsafe objects once discarded by an administrator. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Other sources

Jenkins 2.274 and earlier, LTS 2.263.1 and earlier allows attackers with permission to create or configure various objects to inject crafted content into Old Data Monitor that results in the instantiation of potentially unsafe objects once discarded by an administrator.

Jenkins provides XML REST APIs to configure views, jobs, and other items. When deserialization fails because of invalid data, Jenkins 2.274 and earlier, LTS 2.263.1 and earlier stores invalid object references created through these endpoints in the Old Data Monitor. If an administrator discards the old data, some erroneous data submitted to these endpoints may be persisted.

This allows attackers with View/Create, Job/Create, Agent/Create, or their respective /Configure permissions to inject crafted content into Old Data Monitor that results in the instantiation of potentially unsafe objects when discarded by an administrator.\n\nJenkins 2.275, LTS 2.263.2 does not record submissions from users in Old Data Monitor anymore.

In case of problems, the Java system properties hudson.util.RobustReflectionConverter.recordFailuresForAdmins and hudson.util.RobustReflectionConverter.recordFailuresForAllAuthentications can be set to true to record configuration data submissions from administrators or all users, partially or completely disabling this fix.

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.el7
2:2.0.21-1.rhaos4.5.el7
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.el7
0:4.5.0-202102050524.p0.git.0.9229406.el7
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.el8
0:4.5.0-202102051529.p0.git.3612.61b096a.el8
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.el7
  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.el7
  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.el8
  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 to a version that resolves this vulnerability.

    Fixed in 2.263.2
  16. Configuration

    Set the Java system property hudson.util.RobustReflectionConverter.recordFailuresForAdmins to true to record configuration data submissions from administrators (partially or completely disabling this fix in case of problems).

    Jenkins Java system properties hudson.util.RobustReflectionConverter.recordFailuresForAdmins = true
  17. Configuration

    Set the Java system property hudson.util.RobustReflectionConverter.recordFailuresForAllAuthentications to true to record configuration data submissions from all users/administrators (partially or completely disabling this fix in case of problems).

    Jenkins Java system properties hudson.util.RobustReflectionConverter.recordFailuresForAllAuthentications = true

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:56 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-21604?

The severity of CVE-2021-21604 is high.

2

How can an attacker exploit CVE-2021-21604?

An attacker with permission to create or configure various objects can inject crafted content into Old Data Monitor, causing the instantiation of potentially unsafe objects.

3

Which versions of Jenkins are affected by CVE-2021-21604?

Jenkins versions 2.274 and earlier LTS 2.263.1 and earlier are affected by CVE-2021-21604.

4

How can I fix CVE-2021-21604?

To fix CVE-2021-21604, update to Jenkins version 2.275 or Jenkins LTS version 2.263.2.

5

Where can I find more information about CVE-2021-21604?

You can find more information about CVE-2021-21604 at the following references: [Red Hat Security Advisory RHSA-2021:0423](https://access.redhat.com/errata/RHSA-2021:0423), [CVE-2021-21604](https://access.redhat.com/security/cve/cve-2021-21604), [Red Hat Security Advisory RHSA-2021:0429](https://access.redhat.com/errata/RHSA-2021:0429).

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