CVE-2021-21697
First published: Thu Nov 04 2021(Updated: )
Agents are allowed some limited access to files on the Jenkins controller file system. The directories agents are allowed to access in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier include the directories storing build-related information, intended to allow agents to store build-related metadata during build execution. As a consequence, this allows any agent to read and write the contents of any build directory stored in Jenkins with very few restrictions (`build.xml` and some Pipeline-related metadata). Jenkins 2.319, LTS 2.303.3 prevents agents from accessing contents of build directories unless it’s for builds currently running on the agent attempting to access the directory. Update [Pipeline: Nodes and Processes](https://plugins.jenkins.io/workflow-durable-task-step/) to version 2.40 or newer for Jenkins to associate Pipeline `node` blocks with the agent they’re running on for this fix. If you are unable to immediately upgrade to Jenkins 2.319, LTS 2.303.3, you can install the [Remoting Security Workaround Plugin](https://www.jenkins.io/redirect/remoting-security-workaround/). It will prevent all agent-to-controller file access using `FilePath` APIs. Because it is more restrictive than Jenkins 2.319, LTS 2.303.3, more plugins are incompatible with it. Make sure to read the plugin documentation before installing it.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Jenkins | <=2.303.2 | |
| Jenkins Jenkins | <=2.318 | |
| redhat/jenkins | <2.319 | 2.319 |
| redhat/jenkins LTS | <2.303.3 | 2.303.3 |
| maven/org.jenkins-ci.main:jenkins-core | <=2.303.2 | 2.303.3 |
| maven/org.jenkins-ci.main:jenkins-core | >=2.304<=2.318 | 2.319 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2021-21697
- https://www.jenkins.io/security/advisory/2021-11-04/#SECURITY-2428
- http://www.openwall.com/lists/oss-security/2021/11/04/3
- https://github.com/jenkinsci/jenkins/commit/cf388d2a04e6016d23eb93fa3cc804f2554b98f0
- https://github.com/jenkinsci/jenkins/commit/eae33841b587da787f37d5b6c8451d483edc04d9
- https://github.com/advisories/GHSA-cv2w-q8c3-xjv7 (Advisory)
- https://access.redhat.com/errata/RHSA-2021:4833
- https://access.redhat.com/errata/RHSA-2021:4829
- https://access.redhat.com/errata/RHSA-2021:4801
- https://access.redhat.com/errata/RHSA-2021:4799
- https://access.redhat.com/errata/RHSA-2021:4827
- https://access.redhat.com/security/cve/cve-2021-21697
- https://bugzilla.redhat.com/show_bug.cgi?id=2020345
Frequently Asked Questions
What is the vulnerability ID?
The vulnerability ID is CVE-2021-21697.
What is the severity of CVE-2021-21697?
The severity of CVE-2021-21697 is critical (9.1).
Which versions of Jenkins are affected by CVE-2021-21697?
Jenkins 2.318 and earlier, LTS 2.303.2 and earlier are affected by CVE-2021-21697.
How can I fix CVE-2021-21697?
To fix CVE-2021-21697, upgrade to Jenkins 2.319 or Jenkins LTS 2.303.3.
Where can I find more information about CVE-2021-21697?
You can find more information about CVE-2021-21697 on the Open Wall website, the Jenkins security advisory, and the Red Hat website.
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/remedy
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- collector/github-advisory
- alias/GHSA-cv2w-q8c3-xjv7
- alias/CVE-2021-21697
- collector/github-advisory-latest
- collector/nvd-api
- collector/nvd-cve
- collector/nvd-index
- collector/redhat-bugzilla
- source/Red Hat
- agent/software-canonical-lookup
- package-manager/maven
- vendor/jenkins
- canonical/jenkins jenkins
- version/jenkins jenkins/2.303.2
- version/jenkins jenkins/2.318
- package-manager/redhat