gsd-2022-39299
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
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.
Aliases
Aliases
CVE-2022-39299


To clipboard 

{
   GSD: {
      alias: "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.",
      id: "GSD-2022-39299",
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2022-39299",
         ],
         details: "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.",
         id: "GSD-2022-39299",
         modified: "2023-12-13T01:19:20.647775Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "security-advisories@github.com",
            ID: "CVE-2022-39299",
            STATE: "PUBLIC",
            TITLE: "Signature bypass via multiple root elements in Passport-SAML",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "passport-saml",
                              version: {
                                 version_data: [
                                    {
                                       version_value: "< 3.2.2",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "node-saml",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "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.",
               },
            ],
         },
         impact: {
            cvss: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 7.4,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
               version: "3.1",
            },
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "CWE-347: Improper Verification of Cryptographic Signature",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
                  refsource: "CONFIRM",
                  url: "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
               },
               {
                  name: "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
                  refsource: "MISC",
                  url: "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
               },
               {
                  name: "http://packetstormsecurity.com/files/169826/Node-saml-Root-Element-Signature-Bypass.html",
                  refsource: "MISC",
                  url: "http://packetstormsecurity.com/files/169826/Node-saml-Root-Element-Signature-Bypass.html",
               },
            ],
         },
         source: {
            advisory: "GHSA-m974-647v-whv7",
            discovery: "UNKNOWN",
         },
      },
      "gitlab.com": {
         advisories: [
            {
               affected_range: "<4.0.0-beta.5",
               affected_versions: "All versions before 4.0.0-beta.5",
               cwe_ids: [
                  "CWE-1035",
                  "CWE-347",
                  "CWE-937",
               ],
               date: "2022-10-13",
               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.",
               fixed_versions: [
                  "4.0.0-beta.5",
               ],
               identifier: "CVE-2022-39299",
               identifiers: [
                  "GHSA-m974-647v-whv7",
                  "CVE-2022-39299",
               ],
               not_impacted: "All versions starting from 4.0.0-beta.5",
               package_slug: "npm/@node-saml/node-saml",
               pubdate: "2022-10-12",
               solution: "Upgrade to version 4.0.0-beta.5 or above. *Note*: 4.0.0-beta.5 may be an unstable version. Use caution.",
               title: "Improper Verification of Cryptographic Signature",
               urls: [
                  "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
                  "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
                  "https://github.com/node-saml/passport-saml/releases/tag/v3.2.2",
                  "https://nvd.nist.gov/vuln/detail/CVE-2022-39299",
                  "https://github.com/advisories/GHSA-m974-647v-whv7",
               ],
               uuid: "dce5d9be-18de-4a12-93ce-9caede5cad03",
            },
            {
               affected_range: "<4.0.0-beta.3",
               affected_versions: "All versions before 4.0.0-beta.3",
               cwe_ids: [
                  "CWE-1035",
                  "CWE-347",
                  "CWE-937",
               ],
               date: "2022-10-13",
               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.",
               fixed_versions: [
                  "4.0.0-beta.3",
               ],
               identifier: "CVE-2022-39299",
               identifiers: [
                  "GHSA-m974-647v-whv7",
                  "CVE-2022-39299",
               ],
               not_impacted: "All versions starting from 4.0.0-beta.3",
               package_slug: "npm/@node-saml/passport-saml",
               pubdate: "2022-10-12",
               solution: "Upgrade to version 4.0.0-beta.3 or above. *Note*: 4.0.0-beta.3 may be an unstable version. Use caution.",
               title: "Improper Verification of Cryptographic Signature",
               urls: [
                  "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
                  "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
                  "https://github.com/node-saml/passport-saml/releases/tag/v3.2.2",
                  "https://nvd.nist.gov/vuln/detail/CVE-2022-39299",
                  "https://github.com/advisories/GHSA-m974-647v-whv7",
               ],
               uuid: "3f191e12-d3c6-4f0c-b57f-80e96c50cd21",
            },
            {
               affected_range: "<4.0.0-beta.5",
               affected_versions: "All versions before 4.0.0-beta.5",
               cwe_ids: [
                  "CWE-1035",
                  "CWE-347",
                  "CWE-937",
               ],
               date: "2022-10-13",
               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.",
               fixed_versions: [
                  "4.0.0-beta.5",
               ],
               identifier: "CVE-2022-39299",
               identifiers: [
                  "GHSA-m974-647v-whv7",
                  "CVE-2022-39299",
               ],
               not_impacted: "All versions starting from 4.0.0-beta.5",
               package_slug: "npm/node-saml",
               pubdate: "2022-10-12",
               solution: "Upgrade to version 4.0.0-beta.5 or above. *Note*: 4.0.0-beta.5 may be an unstable version. Use caution.",
               title: "Improper Verification of Cryptographic Signature",
               urls: [
                  "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
                  "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
                  "https://github.com/node-saml/passport-saml/releases/tag/v3.2.2",
                  "https://nvd.nist.gov/vuln/detail/CVE-2022-39299",
                  "https://github.com/advisories/GHSA-m974-647v-whv7",
               ],
               uuid: "ee3ccfc3-e6c3-4aa4-b648-1d0b12da5ce1",
            },
            {
               affected_range: "<3.2.2||=4.0.0",
               affected_versions: "All versions before 3.2.2, version 4.0.0",
               cvss_v3: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
               cwe_ids: [
                  "CWE-1035",
                  "CWE-347",
                  "CWE-937",
               ],
               date: "2023-01-20",
               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.",
               fixed_versions: [
                  "3.2.2",
               ],
               identifier: "CVE-2022-39299",
               identifiers: [
                  "CVE-2022-39299",
                  "GHSA-m974-647v-whv7",
               ],
               not_impacted: "All versions starting from 3.2.2 before 4.0.0, all versions after 4.0.0",
               package_slug: "npm/passport-saml",
               pubdate: "2022-10-12",
               solution: "Upgrade to version 3.2.2 or above.",
               title: "Improper Verification of Cryptographic Signature",
               urls: [
                  "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
                  "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
                  "https://github.com/node-saml/passport-saml/releases/tag/v3.2.2",
                  "https://nvd.nist.gov/vuln/detail/CVE-2022-39299",
                  "https://github.com/advisories/GHSA-m974-647v-whv7",
               ],
               uuid: "a7de65bb-4081-4f6f-ba50-063dfe65a474",
            },
         ],
      },
      "nvd.nist.gov": {
         configurations: {
            CVE_data_version: "4.0",
            nodes: [
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta2:*:*:*:node.js:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta3:*:*:*:node.js:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta4:*:*:*:node.js:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:passport-saml_project:passport-saml:4.0.0:beta1:*:*:*:node.js:*:*",
                        cpe_name: [],
                        vulnerable: true,
                     },
                     {
                        cpe23Uri: "cpe:2.3:a:passport-saml_project:passport-saml:*:*:*:*:*:node.js:*:*",
                        cpe_name: [],
                        versionEndExcluding: "3.2.2",
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
            ],
         },
         cve: {
            CVE_data_meta: {
               ASSIGNER: "security-advisories@github.com",
               ID: "CVE-2022-39299",
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "en",
                     value: "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.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "en",
                           value: "CWE-347",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
                     refsource: "CONFIRM",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://github.com/node-saml/passport-saml/security/advisories/GHSA-m974-647v-whv7",
                  },
                  {
                     name: "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
                     refsource: "MISC",
                     tags: [
                        "Patch",
                        "Third Party Advisory",
                     ],
                     url: "https://github.com/node-saml/passport-saml/commit/8b7e3f5a91c8e5ac7e890a0c90bc7491ce33155e",
                  },
                  {
                     name: "http://packetstormsecurity.com/files/169826/Node-saml-Root-Element-Signature-Bypass.html",
                     refsource: "MISC",
                     tags: [
                        "Third Party Advisory",
                        "VDB Entry",
                     ],
                     url: "http://packetstormsecurity.com/files/169826/Node-saml-Root-Element-Signature-Bypass.html",
                  },
               ],
            },
         },
         impact: {
            baseMetricV3: {
               cvssV3: {
                  attackComplexity: "HIGH",
                  attackVector: "NETWORK",
                  availabilityImpact: "HIGH",
                  baseScore: 8.1,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
                  version: "3.1",
               },
               exploitabilityScore: 2.2,
               impactScore: 5.9,
            },
         },
         lastModifiedDate: "2023-01-20T14:24Z",
         publishedDate: "2022-10-12T21:15Z",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • 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.