CVE-2022-39299
HIGHCVE-2022-39299 is a high-severity (CVSS 7.4) CWE-347 vulnerability in passport-saml. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2022-39299 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Signature bypass via multiple root elements in Passport-SAML
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
passport-samlnpmnode-samlnpm@node-saml/node-samlnpmDescription
Passport-SAML is a SAML 2.0 authentication provider for Passport, the Node.js authentication library. A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered. Users should upgrade to passport-saml version 3.2.2 or newer. The issue was also present in the beta releases of node-saml before version 4.0.0-beta.5. If you cannot upgrade, disabling SAML authentication may be done as a workaround.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | passport-saml | all versions | 3.2.2 |
| 📦npm | node-saml | all versions | 4.0.0-beta.5 |
| 📦npm | @node-saml/node-saml | all versions | 4.0.0-beta.5 |
| 📦npm | @node-saml/passport-saml | all versions | 4.0.0-beta.3 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passport-saml. 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.
Fix
Update passport-saml to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39299 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2022-39299 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 CVE-2022-39299. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-39299 in your dependencies?
O3 detects CVE-2022-39299 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.