GitHub Advisoryadvisory · Maven

GHSA-6q4g-84f3-mw74 Improper handling of equivalent directory names on Windows in Jenkins

MEDIUM Published 2022-05-24 Modified 2022-12-15 Official page ↗
Aliases
CVE-2021-21682
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:L/I:L/A:L
Weaknesses
CWE-42
Reviewed
2022-12-15

Affected packages

• Maven org.jenkins-ci.main:jenkins-core: >= 2.304, < 2.315 → fixed in 2.315 • Maven org.jenkins-ci.main:jenkins-core: < 2.303.2 → fixed in 2.303.2

Description

Jenkins stores jobs and other entities on disk using their name shown on the UI as file and folder names. On Windows, when specifying a file or folder with a trailing dot character (`example.`), the file or folder will be treated as if that character was not present (`example`). As both are legal names for jobs and other entities in Jenkins 2.314 and earlier, LTS 2.303.1 and earlier, this could allow users with the appropriate permissions to change or replace configurations of jobs and other entities. Jenkins 2.315, LTS 2.303.2 does not allow names of jobs and other entities to end with a dot character.

Related

Alias · CVE (1)

  • CVE-2021-21682 Jenkins 2.314 and earlier, LTS 2.303.1 and earlier accepts names of jobs and other entities with a trailing dot character, potentially… vulnerability

Weakness · CWE (1)

  • CWE-42 Path Equivalence: 'filename.' (Trailing Dot) weakness

References