First published: Wed Oct 25 2017(Updated: )
A signature-validation bypass issue was discovered in SimpleSAMLphp through 1.14.16. A SimpleSAMLphp Service Provider using SAML 1.1 will regard as valid any unsigned SAML response containing more than one signed assertion, provided that the signature of at least one of the assertions is valid. Attributes contained in all the assertions received will be merged and the entityID of the first assertion received will be used, allowing an attacker to impersonate any user of any IdP given an assertion signed by the targeted IdP.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/simplesamlphp/simplesamlphp | <1.14.17 | |
debian/simplesamlphp | 1.16.3-1+deb10u2 1.16.3-1+deb10u1 1.19.0-1 1.19.7-1 | |
composer/simplesamlphp/simplesamlphp | <1.14.17 | 1.14.17 |
SimpleSAMLphp | <=1.14.16 | |
Debian GNU/Linux | =7.0 | |
Debian GNU/Linux | =8.0 | |
Debian GNU/Linux | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-18122 has been rated as a moderate severity vulnerability due to the potential for unauthorized access to sensitive information.
To fix CVE-2017-18122, upgrade SimpleSAMLphp to version 1.14.17 or later.
Versions of SimpleSAMLphp prior to 1.14.17 are affected by CVE-2017-18122.
Yes, CVE-2017-18122 specifically affects SimpleSAMLphp Service Providers that utilize SAML 1.1.
CVE-2017-18122 addresses a signature-validation bypass issue that can compromise the integrity of SAML responses.