GitHub Advisoryadvisory · Maven

GHSA-c735-g9f2-2mvp Cross-Site Request Forgery in Jenkins

HIGH Published 2022-05-24 Modified 2024-03-12 Official page ↗
Aliases
CVE-2020-2160
Ecosystem
Maven
Packages
org.jenkins-ci.main:jenkins-core
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weaknesses
CWE-352, CWE-435
Reviewed
2022-06-24

Affected packages

• Maven org.jenkins-ci.main:jenkins-core: < 2.204.6 → fixed in 2.204.6 • Maven org.jenkins-ci.main:jenkins-core: >= 2.205, < 2.228 → fixed in 2.228

Description

An extension point in Jenkins allows selectively disabling cross-site request forgery (CSRF) protection for specific URLs. Implementations of that extension point received a different representation of the URL path than the Stapler web framework uses to dispatch requests in Jenkins 2.227 and earlier, LTS 2.204.5 and earlier. This discrepancy allowed attackers to craft URLs that would bypass the CSRF protection of any target URL. Jenkins now uses the same representation of the URL path to decide whether CSRF protection is needed for a given URL as the Stapler web framework uses. In case of problems, administrators can disable this security fix by setting the system property `hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO` to `true`. As an additional safeguard, semicolon (`;`) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property `jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath` to `true`.

Related

Alias · CVE (1)

  • CVE-2020-2160 Jenkins 2.227 and earlier, LTS 2.204.5 and earlier uses different representations of request URL paths, which allows attackers to craft… vulnerability

Weakness · CWE (2)

  • CWE-352 Cross-Site Request Forgery weakness
  • CWE-435 Improper Interaction Between Multiple Correctly-Behaving Entities weakness

References