Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-923w-2xv2-7pr8

HIGH

GHSA-923w-2xv2-7pr8 is a high-severity (CVSS 7.5) CWE-347 vulnerability in simplesamlphp/saml2. O3 Security confirms whether GHSA-923w-2xv2-7pr8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SimpleSAMLphp Improper Verification of Cryptographic Signature

Also known asCVE-2018-7644
Published
May 13, 2022
Updated
Apr 25, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

Blast Radius

3 pkgs affected
🐘simplesamlphp/saml2🐘simplesamlphp/saml2🐘simplesamlphp/saml2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The XmlSecLibs library as used in the saml2 library in SimpleSAMLphp before 1.15.3 incorrectly verifies signatures on SAML assertions, allowing a remote attacker to construct a crafted SAML assertion on behalf of an Identity Provider that would pass as cryptographically valid, thereby allowing them to impersonate a user from that Identity Provider, aka a key confusion issue.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsimplesamlphp/saml2all versions1.10.5
🐘Packagistsimplesamlphp/saml22.0&&< 2.3.72.3.7
🐘Packagistsimplesamlphp/saml23.0&&< 3.1.33.1.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simplesamlphp/saml2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update simplesamlphp/saml2 to 1.10.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-923w-2xv2-7pr8 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-923w-2xv2-7pr8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-923w-2xv2-7pr8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The XmlSecLibs library as used in the saml2 library in SimpleSAMLphp before 1.15.3 incorrectly verifies signatures on SAML assertions, allowing a remote attacker to construct a crafted SAML assertion on behalf of an Identity Provider that would pass as cryptographically valid, thereby allowing them to impersonate a user from that Identity Provider, aka a key confusion issue.
O3 Security · Impact-Aware SCA

Is GHSA-923w-2xv2-7pr8 in your dependencies?

O3 detects GHSA-923w-2xv2-7pr8 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.