Skip to content

SimpleSAMLphp vulnerable to XXE in parsing SAML messages

High severity GitHub Reviewed Published Dec 2, 2024 in simplesamlphp/simplesamlphp • Updated Dec 4, 2024
Withdrawn This advisory was withdrawn on Dec 4, 2024

Package

composer simplesamlphp/simplesamlphp (Composer)

Affected versions

>= 2.3.0, < 2.3.4
>= 2.2.0, < 2.2.4
>= 2.1.0, < 2.1.7
< 2.0.15

Patched versions

2.3.4
2.2.4
2.1.7
2.0.15

Description

Withdrawn Advisory

This advisory has been withdrawn because the vulnerability affects users of the SimpleSAMLphp tarball, not the SimpleSAMLphp Composer package. The underlying information about CVE-2024-52596 is still valid.

Original Description

Summary

When loading an (untrusted) XML document, for example the SAMLResponse, it's possible to induce an XXE.

Mitigation:

Remove the LIBXML_DTDLOAD | LIBXML_DTDATTR options from $options is in: https://github.com/simplesamlphp/saml2/blob/717c0adc4877ebd58428637e5626345e59fa0109/src/SAML2/DOMDocumentFactory.php#L41

Background / details

To be published on Dec 8th

References

@tvdijen tvdijen published to simplesamlphp/simplesamlphp Dec 2, 2024
Published to the GitHub Advisory Database Dec 2, 2024
Reviewed Dec 2, 2024
Withdrawn Dec 4, 2024
Last updated Dec 4, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-j5g2-q29x-cw3h

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.