Skip to content
Fencer Intel
high 7.5

CVE-2018-7644 json

SimpleSAMLphp Improper Verification of Cryptographic Signature

published 2018-03-05 8 y ago modified 2026-06-17 4 mo ago also GHSA-923w-2xv2-7pr8 , EUVD-2022-3265

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

The XmlSecLibs library as used in the saml2 library in SimpleSAMLphp before 1.15.3 incorrectly verifies signatures on SAML assertions, allowing a remote attacker to construct a crafted SAML assertion on behalf of an Identity Provider that would pass as cryptographically valid, thereby allowing them to impersonate a user from that Identity Provider, aka a key confusion issue.

Patch / fix

  • packagist simplesamlphp/saml2 1.10.5, 2.3.7, 3.1.3
  • simplesamlphp simplesamlphp 1.15.3
  • simplesamlphp Debian 14, Debian 12 1.15.3-1

debian advisories DEBIAN-CVE-2018-7644

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-7644 updated cvss 5.9

php-simplesamlphp-saml2: Signature Validation Bypass

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.45% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist simplesamlphp/saml2
<1.10.5
>=2.0, <2.3.7
>=3.0, <3.1.3
1.10.5
2.3.7
3.1.3

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

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.