ghsa-m974-647v-whv7
Vulnerability from github
Published
2022-10-12 22:05
Modified
2022-10-18 03:11
Severity ?
Summary
Signature bypass via multiple root elements
Details
Impact
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.
Patches
Users 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.
Workarounds
Disable SAML authentication.
References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory: * Open a discussion in the node-saml repo
Credits
- Felix Wilhelm of Google Project Zero
{ "affected": [ { "package": { "ecosystem": "npm", "name": "passport-saml" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "3.2.2" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "node-saml" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "4.0.0-beta.5" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "@node-saml/node-saml" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "4.0.0-beta.5" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "@node-saml/passport-saml" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "4.0.0-beta.3" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2022-39299" ], "database_specific": { "cwe_ids": [ "CWE-347" ], "github_reviewed": true, "github_reviewed_at": "2022-10-12T22:05:41Z", "nvd_published_at": "2022-10-12T21:15:00Z", "severity": "HIGH" }, "details": "### 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", "id": "GHSA-m974-647v-whv7", "modified": "2022-10-18T03:11:22Z", "published": "2022-10-12T22:05:41Z", "references": [ { "type": "WEB", "url": "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-39299" }, { "type": "WEB", "url": "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e" }, { "type": "PACKAGE", "url": "https://github.com/node-saml/passport-saml" }, { "type": "WEB", "url": "https://github.com/node-saml/passport-saml/releases/tag/v3.2.2" }, { "type": "WEB", "url": "http://packetstormsecurity.com/files/169826/Node-saml-Root-Element-Signature-Bypass.html" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ], "summary": "Signature bypass via multiple root elements" }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.