ghsa-f33f-hhx9-6j4m
Vulnerability from github
Published
2022-05-24 17:38
Modified
2022-05-24 17:38
Details

Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2020-8287",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-444",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2021-01-06T21:15:00Z",
      severity: "MODERATE",
   },
   details: "Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.",
   id: "GHSA-f33f-hhx9-6j4m",
   modified: "2022-05-24T17:38:08Z",
   published: "2022-05-24T17:38:08Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2020-8287",
      },
      {
         type: "WEB",
         url: "https://hackerone.com/reports/1002188",
      },
      {
         type: "WEB",
         url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2022/12/msg00009.html",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H472D5HPXN6RRXCNFML3BK5OYC52CXF2",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/K4I6MZNC7C7VIDQR267OL4TVCI3ZKAC4",
      },
      {
         type: "WEB",
         url: "https://nodejs.org/en/blog/vulnerability/january-2021-security-releases",
      },
      {
         type: "WEB",
         url: "https://security.gentoo.org/glsa/202101-07",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20210212-0003",
      },
      {
         type: "WEB",
         url: "https://www.debian.org/security/2021/dsa-4826",
      },
      {
         type: "WEB",
         url: "https://www.oracle.com/security-alerts/cpujan2021.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
         type: "CVSS_V3",
      },
   ],
}


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.


Loading…

Loading…

Loading…

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.