{"answers":{"affected":"2 open source packages ship an affected version, including node-saml. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39300 in the wild and no public exploit code.","fix":"Upgrade node-saml to 4.0.0-beta.5 or later.","what":"CVE-2022-39300 is a high-severity authentication bypass vulnerability in node-saml, published on 13 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39300 and fix it if it is affected.\n\nWhat it is: CVE-2022-39300 is a high-severity authentication bypass vulnerability in node-saml, published on 13 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-39300 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node-saml (npm): affected all versions; fixed in 4.0.0-beta.5\n- node-saml (npm): affected all versions; fixed in 4.0.0-beta.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-39300/ (Markdown: https://insights.sbomify.com/CVE-2022-39300/index.md)","id":"CVE-2022-39300","markdown":"https://insights.sbomify.com/CVE-2022-39300/index.md","name":"CVE-2022-39300","record":{"aliases":["GHSA-5p8w-2mvw-38pv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js SAML library","requires_auth":"none","summary":"Remote attackers can bypass SAML authentication in node-saml by exploiting signature validation flaws with multiple root elements.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"node_saml","vendor":"node_saml_project"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"node SAML is a SAML 2.0 library based on the SAML implementation of passport-saml. 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 node-saml version 4.0.0-beta5 or newer. Disabling SAML authentication may be done as a workaround.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Signature bypass via multiple root elements in node-SAML","id":"CVE-2022-39300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"sra-admin is vulnerable to storage cross-site scripting (XSS) via unrestricted file upload","id":"CVE-2022-39301"},"packages":[{"ecosystem":"npm","fixed":["4.0.0-beta.5"],"introduced":["0"],"last_affected":[],"package":"node-saml","purl":null,"source":"GHSA-5p8w-2mvw-38pv"},{"ecosystem":"npm","fixed":["4.0.0-beta.5"],"introduced":["0"],"last_affected":[],"package":"node-saml","purl":"pkg:npm/node-saml","source":"GHSA-5p8w-2mvw-38pv"}],"prev":{"headline":"Signature bypass via multiple root elements in Passport-SAML","id":"CVE-2022-39299"},"products":["node-saml"],"published":"2022-10-13","related":[{"cvss_score":5.3,"headline":"@node-saml/node-saml's validatePostRequestAsync does not include checkTimestampsValidityError","id":"CVE-2023-40178","kev_date_added":null,"published":"2023-08-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["node-saml"]},"summary":"Remote attackers can bypass SAML authentication in node-saml by exploiting signature validation flaws with multiple root elements.","url":"https://insights.sbomify.com/CVE-2022-39300/"}