CVE-2018-7711 is a high-severity (CVSS 8.1) CWE-347 vulnerability in simplesamlphp/saml2. A fix is available for simplesamlphp/saml2 — see the affected versions and patch details below.
SimpleSAMLphp saml2 incorrect signature validation
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
simplesamlphp/saml2🐘simplesamlphp/saml2🐘simplesamlphp/saml2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
HTTPRedirect.php in the saml2 library in SimpleSAMLphp before 1.15.4 has an incorrect check of return values in the signature validation utilities, allowing an attacker to get invalid signatures accepted as valid by forcing an error during validation. This occurs because of a dependency on PHP functionality that interprets a -1 error code as a true boolean value.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | simplesamlphp/saml2 | all versions | 1.10.6composer require simplesamlphp/saml2:^1.10.6 |
| 🐘Packagist | simplesamlphp/saml2 | ≥ 2.0&&< 2.3.8 | 2.3.8composer require simplesamlphp/saml2:^2.3.8 |
| 🐘Packagist | simplesamlphp/saml2 | ≥ 3.0&&< 3.1.4 | 3.1.4composer require simplesamlphp/saml2:^3.1.4 |
Affected Products
debian linuxdebiansaml2simplesamlphpsimplesamlphpsimplesamlphpDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simplesamlphp/saml2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simplesamlphp/saml2 to 1.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7711 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2018-7711 in your dependencies?
Find it across Packagist, including transitive dependencies.