GitHub Advisoryadvisory · Maven

GHSA-w2hv-rcqr-2h7r View name validation bypass in Jenkins

MEDIUM Published 2022-05-24 Modified 2022-12-13 Official page ↗
Aliases
CVE-2021-21640
Ecosystem
Maven
Packages
org.jenkins-ci.main:jenkins-core
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Weaknesses
CWE-240
Reviewed
2022-06-23

Affected packages

• Maven org.jenkins-ci.main:jenkins-core: < 2.277.2 → fixed in 2.277.2 • Maven org.jenkins-ci.main:jenkins-core: >= 2.278, < 2.287 → fixed in 2.287

Description

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.

Related

Alias · CVE (1)

  • CVE-2021-21640 Jenkins 2.286 and earlier, LTS 2.277.1 and earlier does not properly check that a newly created view has an allowed name, allowing… vulnerability

Weakness · CWE (1)

  • CWE-240 Improper Handling of Inconsistent Structural Elements weakness

References