Security Advisories - SimpleSAMLphp

Home » Security Advisories
SimpleSAMLphp is a software product critical for the security of applications and the privacy of users. As such, we take every security issue very seriously, and try to solve them as fast as possible, avoiding any potential damage to both users of this software and end users.
This page contains information about security vulnerabilities, incidents or issues related to SimpleSAMLphp. Read below to learn how to properly report vulnerabilities, as well as to find information about issues already reported and fixed.
In case you find a vulnerability in SimpleSAMLphp, or you want to confirm a possible security issue in the software, please get in touch with us through the github Security page or the respective page for one of the core libraries such as saml2. We will get back to you as soon as possible according to our working hours in Central European Time.
When reporting a security issue, please add as much information as possible to help us identify, confirm, replicate and fix the problem. In particular, remember to include the following information in your report:
Please DO NOT report security incidents related to systems that use SimpleSAMLphp, where this software is not the cause of the incident. Issues related to the use (or misuse) of infrastructure, misconfiguration of the software, malfunction of a particular system or user-related errors should not be reported either. If you are using SimpleSAMLphp to authenticate or login to services, but you don’t know what SimpleSAMLphp is or you are not sure about the nature of the issue, please contact the organization running the service for you.
Finally, be reasonable. We’ll do our best to resolve the issue according to our principles of security and transparency. Every confirmed vulnerability will be published and resolved in a timely manner. All we ask in return is that you contact us privately first in order to avoid any potential damage to those using the software.
SSPSA 202512-01: Signature verification bypass.
SSPSA 202501-01: Signature verification bypass.
SSPSA 202412-01: XXE in parsing SAML messages.
SSPSA 202309-01: Regression in setting of security headers.
SSPSA 202004-01: Information disclosure of source code.
SSPSA 202001-02: Log injection.
SSPSA 202001-01: Cross-site scripting in error reports.
SSPSA 201911-02: Information disclosure.
SSPSA 201911-01: Signature validation bypass.
SSPSA 201907-01: Reflected Cross-Site-Scripting.
SSPSA 201812-01: Credentials exposure in session storage.
SSPSA 201809-03: Multiple XPath injections (xmlseclibs).
SSPSA 201809-02: Dangerous use of file_get_contents (xmlseclibs).
SSPSA 201809-01: Insecure signature validation (xmlseclibs).
SSPSA 201803-01: Incorrect signature validation (in SAML 2.0).
SSPSA 201802-01: Incorrect signature validation (in SAML 2.0).
SSPSA 201801-03: Use of insecure connection charset (sqlauth module).
SSPSA 201801-02: Open redirection protection bypass.
SSPSA 201801-01: Denial of Service in timestamp validation function (SAML2 library).
SSPSA 201710-01: Signature validation bypass (in SAML 1.1).
SSPSA 201709-01: Cross Site Scripting (XSS) in the consentAdmin module.
SSPSA 201708-01: Invalid token creation and validation.
SSPSA 201705-01: Session fixation issue and authentication bypass in the authcrypt module.
SSPSA 201704-02: Authentication context bypass (multiauth module).
SSPSA 201704-01: Unauthenticated encryption in CBC mode.
SSPSA 201703-02: Incorrect IV generation for encryption.
SSPSA 201703-01: Multiple issues due to timing side channels.
SSPSA 201612-04: Incorrect persistent NameID generation.
SSPSA 201612-03: Incorrect signature validation (InfoCard module).
SSPSA 201612-02: Incorrect signature validation (in SAML 1.1).
SSPSA 201612-01: Incorrect signature validation (in SAML 2.0).
SSPSA 201606-01: Link injection in several pages.
SSPSA 201603-01: Information leakage issue in the sanitycheck module.