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

GHSA-pqm6-cgwr-x6pf

HIGH

GHSA-pqm6-cgwr-x6pf is a high-severity (CVSS 8.8) CWE-347 vulnerability in robrichards/xmlseclibs. O3 Security confirms whether GHSA-pqm6-cgwr-x6pf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Signature validation bypass in XmlSecLibs

Also known asCVE-2019-3465
Published
Nov 8, 2019
Updated
Mar 14, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
🐘robrichards/xmlseclibs🐘robrichards/xmlseclibs

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

Rob Richards XmlSecLibs, all versions prior to v3.0.3, as used for example by SimpleSAMLphp, performed incorrect validation of cryptographic signatures in XML messages, allowing an authenticated attacker to impersonate others or elevate privileges by creating a crafted XML message.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistrobrichards/xmlseclibs3.0.0&&< 3.0.43.0.4
🐘Packagistrobrichards/xmlseclibs1.0.0&&< 2.1.12.1.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for robrichards/xmlseclibs. 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 robrichards/xmlseclibs to 3.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pqm6-cgwr-x6pf 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-pqm6-cgwr-x6pf 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-pqm6-cgwr-x6pf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Rob Richards XmlSecLibs, all versions prior to v3.0.3, as used for example by SimpleSAMLphp, performed incorrect validation of cryptographic signatures in XML messages, allowing an authenticated attacker to impersonate others or elevate privileges by creating a crafted XML message.
O3 Security · Impact-Aware SCA

Is GHSA-pqm6-cgwr-x6pf in your dependencies?

O3 detects GHSA-pqm6-cgwr-x6pf across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.