Jenkins SAML Single Sign On (SSO) Plugin vulnerabilities

A missing permission check in Jenkins SAML Single Sign On (SSO) Plugin versions 2.1.0 through 2.3.0 allows attackers with Overall/Read permission to download a string representation of the current security realm.

A missing permission check in Jenkins SAML Single Sign On (SSO) Plugin 2.0.0 and earlier allows attackers with Overall/Read permission to send an HTTP POST request with JSON body containing attacker-specified content to miniOrange's API for sending emails.

The SAML Single Sign On (SSO) plugin in Jenkins version 2.0.0 and earlier contains a cross-site request forgery (CSRF) vulnerability. It allows attackers to send HTTP POST requests with a JSON body containing attacker-specified content to miniOrange's API for sending emails.

Jenkins SAML Single Sign On (SSO) Plugin 2.1.0 and earlier unconditionally disables SSL/TLS certificate validation for connections to miniOrange or the configured IdP to retrieve SAML metadata.

Jenkins SAML Single Sign On (SSO) Plugin version 2.0.2 and earlier does not perform hostname validation when connecting to miniOrange or the configured IdP to retrieve SAML metadata. This could be exploited using a man-in-the-middle attack to intercept these connections.

Missing permission checks in Jenkins SAML Single Sign On (SSO) Plugin 2.0.2 and earlier allow 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.