CVE-2016-9814 json
SimpleSAMLphp SAML2 spoof SAML responses
published 2017-02-16 9 y ago modified 2026-06-17 4 mo ago also GHSA-r8v4-7vwj-983x , EUVD-2022-5133
- cvss
- 9.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
The validateSignature method in the SAML2\Utils class in SimpleSAMLphp before 1.14.10 and simplesamlphp/saml2 library before 1.9.1, 1.10.x before 1.10.3, and 2.x before 2.3.3 allows remote attackers to spoof SAML responses or possibly cause a denial of service (memory consumption) by leveraging improper conversion of return values to boolean.
Patch / fix
- packagist simplesamlphp/saml2 1.8.1, 1.9.1, 1.10.3, 2.3.3
- simplesamlphp Debian 14, Debian 12 1.14.10-1
debian advisories DEBIAN-CVE-2016-9814
Exploit prediction
2.41% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| NVD | 2.0 | 8.5 | AV:N/AC:L/Au:N/C:N/I:P/A:C |
| GitHub | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | simplesamlphp/saml2 | >=1.10, <1.10.3 <1.8.1 >=1.9.0, <1.9.1 >=2.0, <2.3.3 |
1.10.3 1.8.1 1.9.1 2.3.3 |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
simplesamlphp.org
/security/201612-01
web, vendor-advisory
-
securityfocus.com
/bid/94730
vdb-entry, web, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2018/03/msg00001.html
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2016-9814
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/simplesamlphp/saml2/CVE-2016-9814.yaml
web
-
github.com
/simplesamlphp/simplesamlphp
package
Sources
- CVE List CVE-2016-9814
- GitHub Advisory GHSA-r8v4-7vwj-983x
- NVD CVE-2016-9814
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.