Skip to content
Fencer Intel
high 7.5

CVE-2018-6519 json

SimpleSAMLphp SAML2 library Regular Expression Denial of Service vulnerability

published 8y ago modified 4mo ago also GHSA-hhm8-2j4g-mpgg , EUVD-2022-4159

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

Summary

The SAML2 library before 1.10.4, 2.x before 2.3.5, and 3.x before 3.1.1 in SimpleSAMLphp has a Regular Expression Denial of Service vulnerability for fraction-of-seconds data in a timestamp.

Patch / fix

  • packagist simplesamlphp/saml2 1.10.4, 2.3.5, 3.1.1
  • simplesamlphp saml2 1.10.4, 2.3.5, 3.1.1
  • simplesamlphp Debian 14, Debian 12 1.15.2-1

debian advisories DEBIAN-CVE-2018-6519

Is CVE-2018-6519 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-6519 updated cvss 5.7

php-simplesamlphp-saml2: Denial of Service in xs:DateTime timestamp in SAML2 library

  • 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.70% chance of exploitation in the next 30 days, higher than 77% 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:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
packagist simplesamlphp/saml2
<1.10.4
>=2.0, <2.3.5
>=3.0, <3.1.1
1.10.4
2.3.5
3.1.1

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

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.