CVE-2021-21607: Medium severity Jenkins Jenkins vulnerability
Jenkins 2.274 and earlier, LTS 2.263.1 and earlier does not limit sizes provided as query parameters to graph-rendering URLs, allowing attackers to request crafted URLs that use all available memory in Jenkins, potentially leading to out of memory errors.
Other sources
Jenkins renders several different graphs for features like agent and label usage statistics, memory usage, or various plugin-provided statistics.
Jenkins 2.274 and earlier, LTS 2.263.1 and earlier does not limit the graph size provided as query parameters.
This allows attackers to request or to have legitimate Jenkins users request crafted URLs that rapidly use all available memory in Jenkins, potentially leading to out of memory errors.
Jenkins 2.275, LTS 2.263.2 limits the maximum size of graphs to an area of 10 million pixels. If a larger size is requested, the default size for the graph will be rendered instead.
This threshold can be configured by setting the Java system property hudson.util.Graph.maxArea to a different number on startup.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/jenkinsto a version that resolves this vulnerability.Fixed in 0:2.263.3.1612433584-1.el7 - Upgrade
Upgrade
redhat/conmonto a version that resolves this vulnerability.Fixed in 2:2.0.21-1.rhaos4.5.el7 - Upgrade
Upgrade
redhat/jenkinsto a version that resolves this vulnerability.Fixed in 0:2.263.3.1612434332-1.el7 - Upgrade
Upgrade
redhat/machine-config-daemonto a version that resolves this vulnerability.Fixed in 0:4.5.0-202102050524.p0.git.2594.ff3b8c0.el8 - Upgrade
Upgrade
redhat/openshiftto a version that resolves this vulnerability.Fixed in 0:4.5.0-202102050524.p0.git.0.9229406.el7 - Upgrade
Upgrade
redhat/openshift-ansibleto a version that resolves this vulnerability.Fixed in 0:4.5.0-202102031005.p0.git.0.c6839a2.el7 - Upgrade
Upgrade
redhat/openshift-clientsto a version that resolves this vulnerability.Fixed in 0:4.5.0-202102051529.p0.git.3612.61b096a.el8 - Upgrade
Upgrade
redhat/runcto a version that resolves this vulnerability.Fixed in 0:1.0.0-72.rhaos4.5.giteadfc6b.el8 - Upgrade
Upgrade
redhat/jenkinsto a version that resolves this vulnerability.Fixed in 0:2.263.3.1612434510-1.el8 - Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.275 - Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.263.2 - Upgrade
Upgrade
redhat/jenkinsto a version that resolves this vulnerability.Fixed in 2.275 - Upgrade
Upgrade
redhat/jenkins LTSto a version that resolves this vulnerability.Fixed in 2.263.2 - Upgrade
Upgrade
Jenkinsto a version that resolves this vulnerability.Fixed in 2.275 - Upgrade
Upgrade
Jenkinsto a version that resolves this vulnerability.Fixed in 2.263.2 - Configuration
On Jenkins startup, set the Java system property hudson.util.Graph.maxArea to control the maximum rendered graph size (max area) instead of allowing oversized graph-rendering URLs.
Jenkins hudson.util.Graph.maxArea = 10 million pixels (default in 2.275 and LTS 2.263.2)
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2021-21607?
CVE-2021-21607 is classified as a high severity vulnerability due to its potential for triggering out of memory errors.
How do I fix CVE-2021-21607?
To mitigate CVE-2021-21607, update Jenkins to version 2.263.2 or later, or to 2.275.
What versions of Jenkins are affected by CVE-2021-21607?
CVE-2021-21607 affects Jenkins versions 2.274 and earlier, as well as LTS 2.263.1 and earlier.
What is the impact of CVE-2021-21607?
The impact of CVE-2021-21607 includes the potential for attackers to exploit memory resources, leading to service interruptions.
Who should be aware of CVE-2021-21607?
System administrators and security personnel responsible for Jenkins installations should be aware of CVE-2021-21607 to ensure proper patching.