medium4.3
CVE-2021-21640
View name validation bypass in Jenkins
Impact
Jenkins 2.286 and earlier, LTS 2.277.1 and earlier does not properly check that a newly created view has an allowed name. When a form to create a view is submitted, the name is included twice in the submission. One instance is validated, but the other instance is used to create the value. This allows attackers with View/Create permission to create views with invalid or already-used names. Jenkins 2.287, LTS 2.277.2 uses the same submitted value for validation and view creation.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.main:jenkins-core | >= 2.278, <= 2.286 | 2.287 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Jenkins | Jenkins | through 2.277.1 through 2.286 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- http://www.openwall.com/lists/oss-security/2021/04/07/2
- https://www.jenkins.io/security/advisory/2021-04-07/#SECURITY-1871
- https://github.com/advisories/GHSA-w2hv-rcqr-2h7r
- https://nvd.nist.gov/vuln/detail/CVE-2021-21640
- https://github.com/jenkinsci/jenkins/commit/42e2c74049ddf5e0aca1fe6aadc7b24fdabb5494