CVE-2022-39299 json
Signature bypass via multiple root elements in Passport-SAML
published 4y ago modified 4mo ago also GHSA-m974-647v-whv7 , EUVD-2022-7124
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.5%
- EPSS 4.5% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm passport-saml 3.2.2
- npm node-saml 4.0.0-beta.5
- npm @node-saml/node-saml 4.0.0-beta.5
- npm @node-saml/passport-saml 4.0.0-beta.3
- passport-saml_project passport-saml 3.2.2
Is CVE-2022-39299 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
4.49% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | passport-saml | <3.2.2 |
3.2.2 |
| npm | node-saml | <4.0.0-beta.5 |
4.0.0-beta.5 |
| npm | @node-saml/node-saml | <4.0.0-beta.5 |
4.0.0-beta.5 |
| npm | @node-saml/passport-saml | <4.0.0-beta.3 |
4.0.0-beta.3 |
Affected products
- node-saml passport-saml
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
github.com
/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e
web, patch, third-party-advisory
-
github.com
/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7
web, third-party-advisory
-
packetstormsecurity.com
/files/169826/Node-saml-Root-Element-Signature-Bypass.html
web, third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2022-39299
advisory
-
github.com
/node-saml/passport-saml
package
-
github.com
/node-saml/passport-saml/releases/tag/v3.2.2
web
Sources
- CVE List CVE-2022-39299
- GitHub Advisory GHSA-m974-647v-whv7
- NVD CVE-2022-39299
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.