Skip to content

XXE in parsing SAML messages

High
tvdijen published GHSA-pxm4-r5ph-q2m2 Dec 1, 2024

Package

composer flipboxfactory/saml-core (Composer)

Affected versions

<5.0.1
<4.2.1

Patched versions

None
composer simplesamlphp/saml2 (Composer)
<4.6.14
4.6.14
composer simplesamlphp/saml2-legacy (Composer)
<4.6.14
4.6.14

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:

saml2/src/SAML2/DOMDocumentFactory.php

Line 41 in 717c0ad

$options = LIBXML_DTDLOAD | LIBXML_DTDATTR | LIBXML_NONET | LIBXML_PARSEHUGE;

Background / details

To be published on Dec 8th

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

CVE ID

CVE-2024-52596

Weaknesses

Credits