Description
XML External Entity (XXE) vulnerability in esaml (and its forks) allows an attacker to cause the system to read local files and incorporate their contents into processed SAML documents, and potentially perform SSRF via crafted SAML messages. esaml parses attacker-controlled SAML messages using xmerl_scan:string/2 before signature verification without disabling XML entity expansion. On Erlang/OTP versions before 27, Xmerl allows entities by default, enabling pre-signature XXE attacks. An attacker can cause the host to read local files (e.g., Kubernetes-mounted secrets) into the SAML document. If the attacker is not a trusted SAML SP, signature verification will fail and the document is discarded, but file contents may still be exposed through logs or error messages. This issue affects all versions of esaml, including forks by arekinath, handnot2, and dropbox. Users running on Erlang/OTP 27 or later are not affected due to Xmerl defaulting to entities disabled.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
dropbox esaml
Default version status: affected
pkg:hex/esamlarekinath esaml
Default version status: affected
pkg:github/arekinath/esamlhandnot2 esaml
Default version status: affected
pkg:github/handnot2/esamldropbox esaml
Default version status: affected
pkg:github/dropbox/esamlJump-App esaml
Default version status: affected
deeb84378d5c82153b470e99d24f77c38afca14a to < bab85efde7c136911402a881ca55173759467a26affectedbab85efde7c136911402a881ca55173759467a26unaffected
pkg:github/Jump-App/esaml