First published: Tue May 16 2023(Updated: )
Jenkins SAML Single Sign On(SSO) Plugin 2.0.2 and earlier does not perform permission checks in multiple HTTP endpoints. This allows attackers with Overall/Read permission to send an HTTP request to an attacker-specified URL and parse the response as XML, or parse a local file on the Jenkins controller as XML. As the plugin does not configure its XML parser to prevent XML external entity (XXE) attacks, attackers can have Jenkins parse a crafted XML response that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery. Additionally, these HTTP endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability. SAML Single Sign On(SSO) Plugin 2.1.0 requires POST requests and Overall/Administer permission for the affected HTTP endpoints.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.jenkins.plugins:miniorange-saml-sp | <2.1.0 | 2.1.0 |
Jenkins SAML Single Sign-On | <=2.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-32992 is classified as a high severity vulnerability due to its potential for unauthorized access and data exposure.
To mitigate CVE-2023-32992, upgrade the Jenkins SAML Single Sign On Plugin to version 2.0.3 or later.
CVE-2023-32992 allows attackers to perform unauthorized XML parsing of responses from specified URLs or local files.
CVE-2023-32992 affects Jenkins SAML Single Sign On Plugin versions 2.0.2 and earlier.
Exploitation of CVE-2023-32992 requires an attacker to have Overall/Read permissions on the Jenkins server.