{"id":"CVE-2022-39299","aliases":["EUVD-2022-7124","GHSA-m974-647v-whv7"],"status":"published","title":"Signature bypass via multiple root elements in Passport-SAML","description":"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.","severity":{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.04494,"percentile":0.91556,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-347"],"published":"2022-10-12T00:00:00Z","modified":"2026-10-28T02:31:08Z","exploits":[{"source":"pocgithub","id":"doyensec/CVE-2022-39299_PoC_Generator","title":"doyensec/CVE-2022-39299_PoC_Generator","date":"2022-10-31","url":"https://github.com/doyensec/CVE-2022-39299_PoC_Generator"}],"fixes":[{"ecosystem":"npm","package":"passport-saml","fixed_in":["3.2.2"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"node-saml","fixed_in":["4.0.0-beta.5"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@node-saml/node-saml","fixed_in":["4.0.0-beta.5"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"@node-saml/passport-saml","fixed_in":["4.0.0-beta.3"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"passport-saml","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.2"}]}]},{"source":"ghsa","ecosystem":"npm","package":"node-saml","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0-beta.5"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@node-saml/node-saml","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0-beta.5"}]}]},{"source":"ghsa","ecosystem":"npm","package":"@node-saml/passport-saml","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0-beta.3"}]}]},{"source":"osv","ecosystem":"npm","package":"passport-saml","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.2.2"}]}]},{"source":"osv","ecosystem":"npm","package":"node-saml","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.0.0-beta.5"}]}]},{"source":"osv","ecosystem":"npm","package":"@node-saml/node-saml","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.0.0-beta.5"}]}]},{"source":"osv","ecosystem":"npm","package":"@node-saml/passport-saml","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.0.0-beta.3"}]}]}],"products":[{"vendor":"node-saml","product":"passport-saml"},{"vendor":"passport-saml_project","product":"passport-saml"}],"references":[{"url":"https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7","tags":["x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e","tags":["x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"http://packetstormsecurity.com/files/169826/Node-saml-Root-Element-Signature-Bypass.html","tags":["x_transferred","Third Party Advisory","VDB Entry","web"]},{"url":"https://github.com/node-saml/passport-saml/releases/tag/v3.2.2","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-39299","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-m974-647v-whv7"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/39xxx/CVE-2022-39299.json","tags":["advisory"]},{"url":"https://github.com/node-saml/passport-saml","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2022-39299","title":"Signature bypass via multiple root elements in Passport-SAML","description":"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.","status":"published","published":"2022-10-12T00:00:00Z","modified":"2025-04-23T16:51:09.032Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:34:39.559326Z"}],"euvd":[{"id":"EUVD-2022-7124","description":"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.","status":"published","published":"2022-10-12T00:00:00Z","modified":"2025-04-23T16:51:09Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T20:52:11.891054Z"}],"ghsa":[{"id":"GHSA-m974-647v-whv7","title":"Signature bypass via multiple root elements","description":"### Impact\n\nA 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.\n\n### Patches\n\nUsers should upgrade to passport-saml 3.2.2 or newer. The issue was also present in the beta releases of `node-saml` before v4.0.0-beta.5.\n\n### Workarounds\n\nDisable SAML authentication.\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a discussion in the [node-saml repo](https://github.com/node-saml/node-saml/discussions)\n\n### Credits\n\n* Felix Wilhelm of Google Project Zero\n","status":"published","published":"2022-10-12T22:05:41Z","modified":"2023-01-27T05:03:24Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:36:20.144464Z"}],"nvd":[{"id":"CVE-2022-39299","description":"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.","status":"published","published":"2022-10-12T21:15:09.673Z","modified":"2026-06-17T04:58:05.88Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"secondary"},{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:07:29.52424Z"}],"osv":[{"id":"CVE-2022-39299","title":"Signature bypass via multiple root elements in Passport-SAML","description":"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.","status":"published","published":"2022-10-12T00:00:00Z","modified":"2026-10-28T02:31:08.812611825Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T15:44:26.860704Z"},{"id":"GHSA-m974-647v-whv7","title":"Signature bypass via multiple root elements","description":"### Impact\n\nA 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.\n\n### Patches\n\nUsers should upgrade to passport-saml 3.2.2 or newer. The issue was also present in the beta releases of `node-saml` before v4.0.0-beta.5.\n\n### Workarounds\n\nDisable SAML authentication.\n\n### References\n_Are there any links users can visit to find out more?_\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open a discussion in the [node-saml repo](https://github.com/node-saml/node-saml/discussions)\n\n### Credits\n\n* Felix Wilhelm of Google Project Zero\n","status":"published","published":"2022-10-12T22:05:41Z","modified":"2023-11-08T04:10:18.208725Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T15:46:51.463834Z"}]}}