MediumGHSA-vpr3-cw3h-prw8

SimpleSAMLphp Reflected Cross-site Scripting vulnerability

Published 28 May 2024 · Updated 3 Dec 2024

Is your project on an affected simplesamlphp/simplesamlphp?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=1.12.0 <1.17.3
Fixed in
1.17.3
Update to the fixed version for your release line, for example:composer require simplesamlphp/simplesamlphp:^1.17.3

Details

Background

SimpleSAMLphp uses metadata to determine how to interact with other SAML entities. This metadata includes what’s called endpoints, which are URLs belonging to that entity where SAML messages can be sent. These URLs are used directly by SimpleSAMLphp when a message is sent, either via an HTTP redirection or by automatically posting a form to them.

Description

When sending a SAML message to another entity, SimpleSAMLphp will use the URL of the appropriate endpoint to redirect the user’s browser to it, or craft a form that will be automatically posted to it, depending on the SAML binding used. The URL that’s target of the message is fetched from the stored metadata for the given entity, and that metadata is trusted as correct.

However, if that metadata has been altered by a malicious party (either an attacker or a rogue administrator) to substitute the URLs of the endpoints with javascript code, SimpleSAMLphp was blindly using them without any validation, trusting the contents of the metadata. This would lead to a reflected XSS where the javascript code is sent inline to the web browser, and if SimpleSAMLphp is not using a strict Content Security Policy to forbid inline javascript (which is the case of the default user interface), then the code will be executed in the end user’s browser.

Affected versions

All SimpleSAMLphp versions are affected, up to 1.17.2.

Impact

If metadata is consumed for a rogue entity that includes javascript code in the corresponding endpoints, this javascript code might be run by users trying to access this entity.

Even though it’s unlikely that an administrator would add metadata for an entity that contains such endpoints inadvertently, if metadata is consumed automatically (e.g. using metarefresh) it would be easier to have an scenario like the one described here if a SAML entity is compromised and its metadata modified.

The severity is assessed as medium given the difficulty to exploit the issue.

Is GHSA-vpr3-cw3h-prw8 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected simplesamlphp/simplesamlphp, and gives you the command that fixes it.

More advisories for simplesamlphp/simplesamlphp

  • HighCVE-2026-49284SimpleSAMLphp SP accepts a response from an unexpected IdP when unsigned `Response/InResponseTo` is combined with a signed assertion lacking `SubjectConfirmationData/InResponseTo` · 2 Jul 2026
  • MediumGHSA-ppm4-r2vc-pg74SimpleSAMLphp Information Disclosure vulnerability · 28 May 2024
  • MediumGHSA-7wh8-jrq7-p27fSimpleSAMLphp exposes credentials in session storage · 28 May 2024
  • MediumGHSA-v858-922f-fj9vSimpleSAMLphp Link Injection vulnerability · 28 May 2024
  • MediumCVE-2017-12870SimpleSAMLphp Unauthenticated encryption in CBC mode · 17 May 2022
  • MediumCVE-2017-12871SimpleSAMLphp Incorrect IV generation for encryption · 17 May 2022
All 23 advisories for simplesamlphp/simplesamlphp

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.