GSD-2017-18924

Vulnerability from gsd - Updated: 2023-12-13 01:21
Details
** DISPUTED ** oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states 'As RFC7636 is an extension, I think the claim in the Readme of "RFC 6749 compliant" is valid and not misleading and I also therefore wouldn't describe this as a "vulnerability" with the library per se.'
Aliases
Aliases

{
  "GSD": {
    "alias": "CVE-2017-18924",
    "description": "** DISPUTED ** oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states \u0027As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn\u0027t describe this as a \"vulnerability\" with the library per se.\u0027",
    "id": "GSD-2017-18924"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2017-18924"
      ],
      "details": "** DISPUTED ** oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states \u0027As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn\u0027t describe this as a \"vulnerability\" with the library per se.\u0027",
      "id": "GSD-2017-18924",
      "modified": "2023-12-13T01:21:11.028230Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "cve@mitre.org",
        "ID": "CVE-2017-18924",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "n/a",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "n/a"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "n/a"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "** DISPUTED ** oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states \u0027As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn\u0027t describe this as a \"vulnerability\" with the library per se.\u0027"
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "n/a"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://tools.ietf.org/html/rfc7636",
            "refsource": "MISC",
            "url": "https://tools.ietf.org/html/rfc7636"
          },
          {
            "name": "https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15",
            "refsource": "MISC",
            "url": "https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15"
          },
          {
            "name": "https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467",
            "refsource": "MISC",
            "url": "https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467"
          },
          {
            "name": "https://github.com/oauthjs/node-oauth2-server/issues/637",
            "refsource": "MISC",
            "url": "https://github.com/oauthjs/node-oauth2-server/issues/637"
          },
          {
            "name": "https://github.com/oauthjs/node-oauth2-server/pull/452",
            "refsource": "MISC",
            "url": "https://github.com/oauthjs/node-oauth2-server/pull/452"
          }
        ]
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003c=3.1.1",
          "affected_versions": "All versions up to 3.1.1",
          "cvss_v2": "AV:N/AC:L/Au:N/C:P/I:N/A:N",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-937",
            "CWE-94"
          ],
          "date": "2021-04-22",
          "description": "** DISPUTED ** oauth2-server (aka node-oauth2-server) implements OAuth without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states \u0027As RFC7636 is an extension, I think the claim in the Readme of \"RFC compliant\" is valid and not misleading and I also therefore wouldn\u0027t describe this as a \"vulnerability\" with the library per se.\u0027",
          "fixed_versions": [],
          "identifier": "CVE-2017-18924",
          "identifiers": [
            "GHSA-2fw4-mgq9-39cx",
            "CVE-2017-18924"
          ],
          "not_impacted": "",
          "package_slug": "npm/oauth2-server",
          "pubdate": "2021-04-22",
          "solution": "Unfortunately, there is no solution available yet.",
          "title": "Improper Control of Generation of Code (\u0027Code Injection\u0027)",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2017-18924",
            "https://github.com/oauthjs/node-oauth2-server/issues/637",
            "https://github.com/oauthjs/node-oauth2-server/pull/452",
            "https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467",
            "https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15",
            "https://tools.ietf.org/html/rfc7636",
            "https://github.com/advisories/GHSA-2fw4-mgq9-39cx"
          ],
          "uuid": "8410a1d3-471d-4169-9b67-42e5ea412170"
        }
      ]
    },
    "nvd.nist.gov": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:oauth2-server_project:oauth2-server:*:*:*:*:*:node.js:*:*",
                    "matchCriteriaId": "7FFE5BBB-4620-482D-A32F-D416AA7E4ADA",
                    "versionEndIncluding": "3.1.1",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "descriptions": [
          {
            "lang": "en",
            "value": "oauth2-server (aka node-oauth2-server) through 3.1.1 implements OAuth 2.0 without PKCE. It does not prevent authorization code injection. This is similar to CVE-2020-7692. NOTE: the vendor states \u0027As RFC7636 is an extension, I think the claim in the Readme of \"RFC 6749 compliant\" is valid and not misleading and I also therefore wouldn\u0027t describe this as a \"vulnerability\" with the library per se."
          },
          {
            "lang": "es",
            "value": "** EN DISPUTA ** oauth2-server (tambi\u00e9n se conoce como node-oauth2-server) versiones hasta 3.1.1, implementa OAuth versi\u00f3n 2.0 sin PKCE.\u0026#xa0;No impide la inyecci\u00f3n de c\u00f3digo de autorizaci\u00f3n.\u0026#xa0;Esto es similar a CVE-2020-7692.\u0026#xa0;NOTA: el proveedor declara \"Como RFC7636 es una extensi\u00f3n, considero que la afirmaci\u00f3n en el archivo L\u00e9ame de \"compatible con RFC 6749\" es v\u00e1lida y no enga\u00f1osa y, por lo tanto, tampoco describir\u00eda esto como una \"vulnerabilidad\" con la biblioteca en s\u00ed"
          }
        ],
        "id": "CVE-2017-18924",
        "lastModified": "2024-04-11T00:58:14.003",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": false,
              "baseSeverity": "MEDIUM",
              "cvssData": {
                "accessComplexity": "LOW",
                "accessVector": "NETWORK",
                "authentication": "NONE",
                "availabilityImpact": "NONE",
                "baseScore": 5.0,
                "confidentialityImpact": "PARTIAL",
                "integrityImpact": "NONE",
                "vectorString": "AV:N/AC:L/Au:N/C:P/I:N/A:N",
                "version": "2.0"
              },
              "exploitabilityScore": 10.0,
              "impactScore": 2.9,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": false
            }
          ],
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
                "version": "3.1"
              },
              "exploitabilityScore": 3.9,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2020-10-04T05:15:12.140",
        "references": [
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://codeburst.io/missing-the-point-in-securing-oauth-2-0-83968708b467"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Exploit",
              "Third Party Advisory"
            ],
            "url": "https://github.com/oauthjs/node-oauth2-server/issues/637"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Patch",
              "Third Party Advisory"
            ],
            "url": "https://github.com/oauthjs/node-oauth2-server/pull/452"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Exploit",
              "Third Party Advisory"
            ],
            "url": "https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://tools.ietf.org/html/rfc7636"
          }
        ],
        "sourceIdentifier": "cve@mitre.org",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-94"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…