csaf_opensuse - opensuse-su-2021:3940-1

Vulnerability from csaf_opensuse

Published

2021-12-06 13:43

Modified

2021-12-06 13:43

Summary

Security update for nodejs12

Notes

Title of the patch

Security update for nodejs12

Description of the patch

This update for nodejs12 fixes the following issues: - CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601). - CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602). - CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057). - CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056). - CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055). - CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054). - CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053).

Patchnames

openSUSE-SLE-15.3-2021-3940

CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).

JSON

To clipboard

{
   document: {
      aggregate_severity: {
         namespace: "https://www.suse.com/support/security/rating/",
         text: "important",
      },
      category: "csaf_security_advisory",
      csaf_version: "2.0",
      distribution: {
         text: "Copyright 2024 SUSE LLC. All rights reserved.",
         tlp: {
            label: "WHITE",
            url: "https://www.first.org/tlp/",
         },
      },
      lang: "en",
      notes: [
         {
            category: "summary",
            text: "Security update for nodejs12",
            title: "Title of the patch",
         },
         {
            category: "description",
            text: "This update for nodejs12 fixes the following issues:\n\n- CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601).\n- CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).\n- CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057). \n- CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056). \n- CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055). \n- CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054). \n- CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053). \n",
            title: "Description of the patch",
         },
         {
            category: "details",
            text: "openSUSE-SLE-15.3-2021-3940",
            title: "Patchnames",
         },
         {
            category: "legal_disclaimer",
            text: "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).",
            title: "Terms of use",
         },
      ],
      publisher: {
         category: "vendor",
         contact_details: "https://www.suse.com/support/security/contact/",
         name: "SUSE Product Security Team",
         namespace: "https://www.suse.com/",
      },
      references: [
         {
            category: "external",
            summary: "SUSE ratings",
            url: "https://www.suse.com/support/security/rating/",
         },
         {
            category: "self",
            summary: "URL of this CSAF notice",
            url: "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2021_3940-1.json",
         },
         {
            category: "self",
            summary: "URL for openSUSE-SU-2021:3940-1",
            url: "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/LB7JXCGGW7EKOPAS4IDMUQPYHXS3ZUZA/",
         },
         {
            category: "self",
            summary: "E-Mail link for openSUSE-SU-2021:3940-1",
            url: "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/LB7JXCGGW7EKOPAS4IDMUQPYHXS3ZUZA/",
         },
         {
            category: "self",
            summary: "SUSE Bug 1190053",
            url: "https://bugzilla.suse.com/1190053",
         },
         {
            category: "self",
            summary: "SUSE Bug 1190054",
            url: "https://bugzilla.suse.com/1190054",
         },
         {
            category: "self",
            summary: "SUSE Bug 1190055",
            url: "https://bugzilla.suse.com/1190055",
         },
         {
            category: "self",
            summary: "SUSE Bug 1190056",
            url: "https://bugzilla.suse.com/1190056",
         },
         {
            category: "self",
            summary: "SUSE Bug 1190057",
            url: "https://bugzilla.suse.com/1190057",
         },
         {
            category: "self",
            summary: "SUSE Bug 1191601",
            url: "https://bugzilla.suse.com/1191601",
         },
         {
            category: "self",
            summary: "SUSE Bug 1191602",
            url: "https://bugzilla.suse.com/1191602",
         },
         {
            category: "self",
            summary: "SUSE CVE CVE-2021-22959 page",
            url: "https://www.suse.com/security/cve/CVE-2021-22959/",
         },
         {
            category: "self",
            summary: "SUSE CVE CVE-2021-22960 page",
            url: "https://www.suse.com/security/cve/CVE-2021-22960/",
         },
         {
            category: "self",
            summary: "SUSE CVE CVE-2021-37701 page",
            url: "https://www.suse.com/security/cve/CVE-2021-37701/",
         },
         {
            category: "self",
            summary: "SUSE CVE CVE-2021-37712 page",
            url: "https://www.suse.com/security/cve/CVE-2021-37712/",
         },
         {
            category: "self",
            summary: "SUSE CVE CVE-2021-37713 page",
            url: "https://www.suse.com/security/cve/CVE-2021-37713/",
         },
         {
            category: "self",
            summary: "SUSE CVE CVE-2021-39134 page",
            url: "https://www.suse.com/security/cve/CVE-2021-39134/",
         },
         {
            category: "self",
            summary: "SUSE CVE CVE-2021-39135 page",
            url: "https://www.suse.com/security/cve/CVE-2021-39135/",
         },
      ],
      title: "Security update for nodejs12",
      tracking: {
         current_release_date: "2021-12-06T13:43:51Z",
         generator: {
            date: "2021-12-06T13:43:51Z",
            engine: {
               name: "cve-database.git:bin/generate-csaf.pl",
               version: "1",
            },
         },
         id: "openSUSE-SU-2021:3940-1",
         initial_release_date: "2021-12-06T13:43:51Z",
         revision_history: [
            {
               date: "2021-12-06T13:43:51Z",
               number: "1",
               summary: "Current version",
            },
         ],
         status: "final",
         version: "1",
      },
   },
   product_tree: {
      branches: [
         {
            branches: [
               {
                  branches: [
                     {
                        category: "product_version",
                        name: "nodejs12-12.22.7-4.22.1.aarch64",
                        product: {
                           name: "nodejs12-12.22.7-4.22.1.aarch64",
                           product_id: "nodejs12-12.22.7-4.22.1.aarch64",
                        },
                     },
                     {
                        category: "product_version",
                        name: "nodejs12-devel-12.22.7-4.22.1.aarch64",
                        product: {
                           name: "nodejs12-devel-12.22.7-4.22.1.aarch64",
                           product_id: "nodejs12-devel-12.22.7-4.22.1.aarch64",
                        },
                     },
                     {
                        category: "product_version",
                        name: "npm12-12.22.7-4.22.1.aarch64",
                        product: {
                           name: "npm12-12.22.7-4.22.1.aarch64",
                           product_id: "npm12-12.22.7-4.22.1.aarch64",
                        },
                     },
                  ],
                  category: "architecture",
                  name: "aarch64",
               },
               {
                  branches: [
                     {
                        category: "product_version",
                        name: "nodejs12-docs-12.22.7-4.22.1.noarch",
                        product: {
                           name: "nodejs12-docs-12.22.7-4.22.1.noarch",
                           product_id: "nodejs12-docs-12.22.7-4.22.1.noarch",
                        },
                     },
                  ],
                  category: "architecture",
                  name: "noarch",
               },
               {
                  branches: [
                     {
                        category: "product_version",
                        name: "nodejs12-12.22.7-4.22.1.ppc64le",
                        product: {
                           name: "nodejs12-12.22.7-4.22.1.ppc64le",
                           product_id: "nodejs12-12.22.7-4.22.1.ppc64le",
                        },
                     },
                     {
                        category: "product_version",
                        name: "nodejs12-devel-12.22.7-4.22.1.ppc64le",
                        product: {
                           name: "nodejs12-devel-12.22.7-4.22.1.ppc64le",
                           product_id: "nodejs12-devel-12.22.7-4.22.1.ppc64le",
                        },
                     },
                     {
                        category: "product_version",
                        name: "npm12-12.22.7-4.22.1.ppc64le",
                        product: {
                           name: "npm12-12.22.7-4.22.1.ppc64le",
                           product_id: "npm12-12.22.7-4.22.1.ppc64le",
                        },
                     },
                  ],
                  category: "architecture",
                  name: "ppc64le",
               },
               {
                  branches: [
                     {
                        category: "product_version",
                        name: "nodejs12-12.22.7-4.22.1.s390x",
                        product: {
                           name: "nodejs12-12.22.7-4.22.1.s390x",
                           product_id: "nodejs12-12.22.7-4.22.1.s390x",
                        },
                     },
                     {
                        category: "product_version",
                        name: "nodejs12-devel-12.22.7-4.22.1.s390x",
                        product: {
                           name: "nodejs12-devel-12.22.7-4.22.1.s390x",
                           product_id: "nodejs12-devel-12.22.7-4.22.1.s390x",
                        },
                     },
                     {
                        category: "product_version",
                        name: "npm12-12.22.7-4.22.1.s390x",
                        product: {
                           name: "npm12-12.22.7-4.22.1.s390x",
                           product_id: "npm12-12.22.7-4.22.1.s390x",
                        },
                     },
                  ],
                  category: "architecture",
                  name: "s390x",
               },
               {
                  branches: [
                     {
                        category: "product_version",
                        name: "nodejs12-12.22.7-4.22.1.x86_64",
                        product: {
                           name: "nodejs12-12.22.7-4.22.1.x86_64",
                           product_id: "nodejs12-12.22.7-4.22.1.x86_64",
                        },
                     },
                     {
                        category: "product_version",
                        name: "nodejs12-devel-12.22.7-4.22.1.x86_64",
                        product: {
                           name: "nodejs12-devel-12.22.7-4.22.1.x86_64",
                           product_id: "nodejs12-devel-12.22.7-4.22.1.x86_64",
                        },
                     },
                     {
                        category: "product_version",
                        name: "npm12-12.22.7-4.22.1.x86_64",
                        product: {
                           name: "npm12-12.22.7-4.22.1.x86_64",
                           product_id: "npm12-12.22.7-4.22.1.x86_64",
                        },
                     },
                  ],
                  category: "architecture",
                  name: "x86_64",
               },
               {
                  branches: [
                     {
                        category: "product_name",
                        name: "openSUSE Leap 15.3",
                        product: {
                           name: "openSUSE Leap 15.3",
                           product_id: "openSUSE Leap 15.3",
                           product_identification_helper: {
                              cpe: "cpe:/o:opensuse:leap:15.3",
                           },
                        },
                     },
                  ],
                  category: "product_family",
                  name: "SUSE Linux Enterprise",
               },
            ],
            category: "vendor",
            name: "SUSE",
         },
      ],
      relationships: [
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-12.22.7-4.22.1.aarch64 as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
            },
            product_reference: "nodejs12-12.22.7-4.22.1.aarch64",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-12.22.7-4.22.1.ppc64le as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
            },
            product_reference: "nodejs12-12.22.7-4.22.1.ppc64le",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-12.22.7-4.22.1.s390x as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
            },
            product_reference: "nodejs12-12.22.7-4.22.1.s390x",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-12.22.7-4.22.1.x86_64 as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
            },
            product_reference: "nodejs12-12.22.7-4.22.1.x86_64",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-devel-12.22.7-4.22.1.aarch64 as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
            },
            product_reference: "nodejs12-devel-12.22.7-4.22.1.aarch64",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-devel-12.22.7-4.22.1.ppc64le as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
            },
            product_reference: "nodejs12-devel-12.22.7-4.22.1.ppc64le",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-devel-12.22.7-4.22.1.s390x as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
            },
            product_reference: "nodejs12-devel-12.22.7-4.22.1.s390x",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-devel-12.22.7-4.22.1.x86_64 as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
            },
            product_reference: "nodejs12-devel-12.22.7-4.22.1.x86_64",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "nodejs12-docs-12.22.7-4.22.1.noarch as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
            },
            product_reference: "nodejs12-docs-12.22.7-4.22.1.noarch",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "npm12-12.22.7-4.22.1.aarch64 as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
            },
            product_reference: "npm12-12.22.7-4.22.1.aarch64",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "npm12-12.22.7-4.22.1.ppc64le as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
            },
            product_reference: "npm12-12.22.7-4.22.1.ppc64le",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "npm12-12.22.7-4.22.1.s390x as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
            },
            product_reference: "npm12-12.22.7-4.22.1.s390x",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
         {
            category: "default_component_of",
            full_product_name: {
               name: "npm12-12.22.7-4.22.1.x86_64 as component of openSUSE Leap 15.3",
               product_id: "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            },
            product_reference: "npm12-12.22.7-4.22.1.x86_64",
            relates_to_product_reference: "openSUSE Leap 15.3",
         },
      ],
   },
   vulnerabilities: [
      {
         cve: "CVE-2021-22959",
         ids: [
            {
               system_name: "SUSE CVE Page",
               text: "https://www.suse.com/security/cve/CVE-2021-22959",
            },
         ],
         notes: [
            {
               category: "general",
               text: "The parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6.",
               title: "CVE description",
            },
         ],
         product_status: {
            recommended: [
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            ],
         },
         references: [
            {
               category: "external",
               summary: "CVE-2021-22959",
               url: "https://www.suse.com/security/cve/CVE-2021-22959",
            },
            {
               category: "external",
               summary: "SUSE Bug 1191601 for CVE-2021-22959",
               url: "https://bugzilla.suse.com/1191601",
            },
         ],
         remediations: [
            {
               category: "vendor_fix",
               details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
               product_ids: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         scores: [
            {
               cvss_v3: {
                  baseScore: 6.1,
                  baseSeverity: "MEDIUM",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
                  version: "3.1",
               },
               products: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         threats: [
            {
               category: "impact",
               date: "2021-12-06T13:43:51Z",
               details: "moderate",
            },
         ],
         title: "CVE-2021-22959",
      },
      {
         cve: "CVE-2021-22960",
         ids: [
            {
               system_name: "SUSE CVE Page",
               text: "https://www.suse.com/security/cve/CVE-2021-22960",
            },
         ],
         notes: [
            {
               category: "general",
               text: "The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions.",
               title: "CVE description",
            },
         ],
         product_status: {
            recommended: [
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            ],
         },
         references: [
            {
               category: "external",
               summary: "CVE-2021-22960",
               url: "https://www.suse.com/security/cve/CVE-2021-22960",
            },
            {
               category: "external",
               summary: "SUSE Bug 1191602 for CVE-2021-22960",
               url: "https://bugzilla.suse.com/1191602",
            },
         ],
         remediations: [
            {
               category: "vendor_fix",
               details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
               product_ids: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         scores: [
            {
               cvss_v3: {
                  baseScore: 6.1,
                  baseSeverity: "MEDIUM",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
                  version: "3.1",
               },
               products: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         threats: [
            {
               category: "impact",
               date: "2021-12-06T13:43:51Z",
               details: "moderate",
            },
         ],
         title: "CVE-2021-22960",
      },
      {
         cve: "CVE-2021-37701",
         ids: [
            {
               system_name: "SUSE CVE Page",
               text: "https://www.suse.com/security/cve/CVE-2021-37701",
            },
         ],
         notes: [
            {
               category: "general",
               text: "The npm package \"tar\" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\\` and `/` characters as path separators, however `\\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.",
               title: "CVE description",
            },
         ],
         product_status: {
            recommended: [
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            ],
         },
         references: [
            {
               category: "external",
               summary: "CVE-2021-37701",
               url: "https://www.suse.com/security/cve/CVE-2021-37701",
            },
            {
               category: "external",
               summary: "SUSE Bug 1190057 for CVE-2021-37701",
               url: "https://bugzilla.suse.com/1190057",
            },
         ],
         remediations: [
            {
               category: "vendor_fix",
               details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
               product_ids: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         scores: [
            {
               cvss_v3: {
                  baseScore: 8.1,
                  baseSeverity: "HIGH",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H",
                  version: "3.1",
               },
               products: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         threats: [
            {
               category: "impact",
               date: "2021-12-06T13:43:51Z",
               details: "important",
            },
         ],
         title: "CVE-2021-37701",
      },
      {
         cve: "CVE-2021-37712",
         ids: [
            {
               system_name: "SUSE CVE Page",
               text: "https://www.suse.com/security/cve/CVE-2021-37712",
            },
         ],
         notes: [
            {
               category: "general",
               text: "The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 \"short path\" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.",
               title: "CVE description",
            },
         ],
         product_status: {
            recommended: [
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            ],
         },
         references: [
            {
               category: "external",
               summary: "CVE-2021-37712",
               url: "https://www.suse.com/security/cve/CVE-2021-37712",
            },
            {
               category: "external",
               summary: "SUSE Bug 1190056 for CVE-2021-37712",
               url: "https://bugzilla.suse.com/1190056",
            },
         ],
         remediations: [
            {
               category: "vendor_fix",
               details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
               product_ids: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         scores: [
            {
               cvss_v3: {
                  baseScore: 8.1,
                  baseSeverity: "HIGH",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H",
                  version: "3.1",
               },
               products: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         threats: [
            {
               category: "impact",
               date: "2021-12-06T13:43:51Z",
               details: "important",
            },
         ],
         title: "CVE-2021-37712",
      },
      {
         cve: "CVE-2021-37713",
         ids: [
            {
               system_name: "SUSE CVE Page",
               text: "https://www.suse.com/security/cve/CVE-2021-37713",
            },
         ],
         notes: [
            {
               category: "general",
               text: "The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.",
               title: "CVE description",
            },
         ],
         product_status: {
            recommended: [
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            ],
         },
         references: [
            {
               category: "external",
               summary: "CVE-2021-37713",
               url: "https://www.suse.com/security/cve/CVE-2021-37713",
            },
            {
               category: "external",
               summary: "SUSE Bug 1190055 for CVE-2021-37713",
               url: "https://bugzilla.suse.com/1190055",
            },
         ],
         remediations: [
            {
               category: "vendor_fix",
               details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
               product_ids: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         scores: [
            {
               cvss_v3: {
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
               products: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         threats: [
            {
               category: "impact",
               date: "2021-12-06T13:43:51Z",
               details: "important",
            },
         ],
         title: "CVE-2021-37713",
      },
      {
         cve: "CVE-2021-39134",
         ids: [
            {
               system_name: "SUSE CVE Page",
               text: "https://www.suse.com/security/cve/CVE-2021-39134",
            },
         ],
         notes: [
            {
               category: "general",
               text: "`@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. When multiple dependencies differ only in the case of their name, Arborist's internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. For example, a package `pwn-a` could define a dependency in their `package.json` file such as `\"foo\": \"file:/some/path\"`. Another package, `pwn-b` could define a dependency such as `FOO: \"file:foo.tgz\"`. On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed. Anyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above.",
               title: "CVE description",
            },
         ],
         product_status: {
            recommended: [
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            ],
         },
         references: [
            {
               category: "external",
               summary: "CVE-2021-39134",
               url: "https://www.suse.com/security/cve/CVE-2021-39134",
            },
            {
               category: "external",
               summary: "SUSE Bug 1190054 for CVE-2021-39134",
               url: "https://bugzilla.suse.com/1190054",
            },
         ],
         remediations: [
            {
               category: "vendor_fix",
               details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
               product_ids: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         scores: [
            {
               cvss_v3: {
                  baseScore: 8.1,
                  baseSeverity: "HIGH",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H",
                  version: "3.1",
               },
               products: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         threats: [
            {
               category: "impact",
               date: "2021-12-06T13:43:51Z",
               details: "important",
            },
         ],
         title: "CVE-2021-39134",
      },
      {
         cve: "CVE-2021-39135",
         ids: [
            {
               system_name: "SUSE CVE Page",
               text: "https://www.suse.com/security/cve/CVE-2021-39135",
            },
         ],
         notes: [
            {
               category: "general",
               text: "`@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's `node_modules` folder. If the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a `node_modules` symbolic link would have to be employed. 1. A `preinstall` script could replace `node_modules` with a symlink. (This is prevented by using `--ignore-scripts`.) 2. An attacker could supply the target with a git repository, instructing them to run `npm install --ignore-scripts` in the root. This may be successful, because `npm install --ignore-scripts` is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.",
               title: "CVE description",
            },
         ],
         product_status: {
            recommended: [
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
               "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
               "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
            ],
         },
         references: [
            {
               category: "external",
               summary: "CVE-2021-39135",
               url: "https://www.suse.com/security/cve/CVE-2021-39135",
            },
            {
               category: "external",
               summary: "SUSE Bug 1190053 for CVE-2021-39135",
               url: "https://bugzilla.suse.com/1190053",
            },
         ],
         remediations: [
            {
               category: "vendor_fix",
               details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
               product_ids: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         scores: [
            {
               cvss_v3: {
                  baseScore: 8.1,
                  baseSeverity: "HIGH",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H",
                  version: "3.1",
               },
               products: [
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:nodejs12-devel-12.22.7-4.22.1.x86_64",
                  "openSUSE Leap 15.3:nodejs12-docs-12.22.7-4.22.1.noarch",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.aarch64",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.ppc64le",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.s390x",
                  "openSUSE Leap 15.3:npm12-12.22.7-4.22.1.x86_64",
               ],
            },
         ],
         threats: [
            {
               category: "impact",
               date: "2021-12-06T13:43:51Z",
               details: "important",
            },
         ],
         title: "CVE-2021-39135",
      },
   ],
}

cve-2021-39135

Vulnerability from cvelistv5

Published

2021-08-31 17:10

Modified

2024-08-04 01:58

Severity ?

8.2 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Summary

`@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's `node_modules` folder. If the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a `node_modules` symbolic link would have to be employed. 1. A `preinstall` script could replace `node_modules` with a symlink. (This is prevented by using `--ignore-scripts`.) 2. An attacker could supply the target with a git repository, instructing them to run `npm install --ignore-scripts` in the root. This may be successful, because `npm install --ignore-scripts` is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.

References

▼	URL	Tags
	https://www.npmjs.com/package/%40npmcli/arborist	x_refsource_MISC
	https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2	x_refsource_CONFIRM
	https://www.oracle.com/security-alerts/cpuoct2021.html	x_refsource_MISC
	https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf	x_refsource_CONFIRM

Impacted products

	Vendor	Product	Version
	npm	arborist	Version: < 2.8.2

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-04T01:58:18.069Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.npmjs.com/package/%40npmcli/arborist",
               },
               {
                  tags: [
                     "x_refsource_CONFIRM",
                     "x_transferred",
                  ],
                  url: "https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2",
               },
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
               },
               {
                  tags: [
                     "x_refsource_CONFIRM",
                     "x_transferred",
                  ],
                  url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "arborist",
               vendor: "npm",
               versions: [
                  {
                     status: "affected",
                     version: "< 2.8.2",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "`@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's `node_modules` folder. If the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a `node_modules` symbolic link would have to be employed. 1. A `preinstall` script could replace `node_modules` with a symlink. (This is prevented by using `--ignore-scripts`.) 2. An attacker could supply the target with a git repository, instructing them to run `npm install --ignore-scripts` in the root. This may be successful, because `npm install --ignore-scripts` is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-61",
                     description: "CWE-61: UNIX Symbolic Link (Symlink) Following",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-03-08T14:07:30",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.npmjs.com/package/%40npmcli/arborist",
            },
            {
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2",
            },
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
            },
            {
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
            },
         ],
         source: {
            advisory: "GHSA-gmw6-94gg-2rc2",
            discovery: "UNKNOWN",
         },
         title: "UNIX Symbolic Link (Symlink) Following in @npmcli/arborist",
         x_legacyV4Record: {
            CVE_data_meta: {
               ASSIGNER: "security-advisories@github.com",
               ID: "CVE-2021-39135",
               STATE: "PUBLIC",
               TITLE: "UNIX Symbolic Link (Symlink) Following in @npmcli/arborist",
            },
            affects: {
               vendor: {
                  vendor_data: [
                     {
                        product: {
                           product_data: [
                              {
                                 product_name: "arborist",
                                 version: {
                                    version_data: [
                                       {
                                          version_value: "< 2.8.2",
                                       },
                                    ],
                                 },
                              },
                           ],
                        },
                        vendor_name: "npm",
                     },
                  ],
               },
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "eng",
                     value: "`@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project's `node_modules` folder. If the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a `node_modules` symbolic link would have to be employed. 1. A `preinstall` script could replace `node_modules` with a symlink. (This is prevented by using `--ignore-scripts`.) 2. An attacker could supply the target with a git repository, instructing them to run `npm install --ignore-scripts` in the root. This may be successful, because `npm install --ignore-scripts` is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.",
                  },
               ],
            },
            impact: {
               cvss: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "eng",
                           value: "CWE-61: UNIX Symbolic Link (Symlink) Following",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://www.npmjs.com/package/@npmcli/arborist",
                     refsource: "MISC",
                     url: "https://www.npmjs.com/package/@npmcli/arborist",
                  },
                  {
                     name: "https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2",
                     refsource: "CONFIRM",
                     url: "https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2",
                  },
                  {
                     name: "https://www.oracle.com/security-alerts/cpuoct2021.html",
                     refsource: "MISC",
                     url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
                  },
                  {
                     name: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
                     refsource: "CONFIRM",
                     url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
                  },
               ],
            },
            source: {
               advisory: "GHSA-gmw6-94gg-2rc2",
               discovery: "UNKNOWN",
            },
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2021-39135",
      datePublished: "2021-08-31T17:10:10",
      dateReserved: "2021-08-16T00:00:00",
      dateUpdated: "2024-08-04T01:58:18.069Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
}

cve-2021-37713

Vulnerability from cvelistv5

Published

2021-08-31 16:50

Modified

2024-08-04 01:23

Severity ?

8.2 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Summary

The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.

References

▼	URL	Tags
	https://www.npmjs.com/package/tar	x_refsource_MISC
	https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh	x_refsource_CONFIRM
	https://www.oracle.com/security-alerts/cpuoct2021.html	x_refsource_MISC
	https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf	x_refsource_CONFIRM

Impacted products

	Vendor	Product	Version
	npm	node-tar	Version: < 4.4.18 Version: >= 5.0.0, < 5.0.10 Version: >= 6.0.0, < 6.1.9

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-04T01:23:01.533Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.npmjs.com/package/tar",
               },
               {
                  tags: [
                     "x_refsource_CONFIRM",
                     "x_transferred",
                  ],
                  url: "https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh",
               },
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
               },
               {
                  tags: [
                     "x_refsource_CONFIRM",
                     "x_transferred",
                  ],
                  url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "node-tar",
               vendor: "npm",
               versions: [
                  {
                     status: "affected",
                     version: "< 4.4.18",
                  },
                  {
                     status: "affected",
                     version: ">= 5.0.0, < 5.0.10",
                  },
                  {
                     status: "affected",
                     version: ">= 6.0.0, < 6.1.9",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-22",
                     description: "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-03-08T14:07:15",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.npmjs.com/package/tar",
            },
            {
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh",
            },
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
            },
            {
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
            },
         ],
         source: {
            advisory: "GHSA-5955-9wpr-37jh",
            discovery: "UNKNOWN",
         },
         title: "Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization",
         x_legacyV4Record: {
            CVE_data_meta: {
               ASSIGNER: "security-advisories@github.com",
               ID: "CVE-2021-37713",
               STATE: "PUBLIC",
               TITLE: "Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization",
            },
            affects: {
               vendor: {
                  vendor_data: [
                     {
                        product: {
                           product_data: [
                              {
                                 product_name: "node-tar",
                                 version: {
                                    version_data: [
                                       {
                                          version_value: "< 4.4.18",
                                       },
                                       {
                                          version_value: ">= 5.0.0, < 5.0.10",
                                       },
                                       {
                                          version_value: ">= 6.0.0, < 6.1.9",
                                       },
                                    ],
                                 },
                              },
                           ],
                        },
                        vendor_name: "npm",
                     },
                  ],
               },
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "eng",
                     value: "The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.",
                  },
               ],
            },
            impact: {
               cvss: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "eng",
                           value: "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://www.npmjs.com/package/tar",
                     refsource: "MISC",
                     url: "https://www.npmjs.com/package/tar",
                  },
                  {
                     name: "https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh",
                     refsource: "CONFIRM",
                     url: "https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh",
                  },
                  {
                     name: "https://www.oracle.com/security-alerts/cpuoct2021.html",
                     refsource: "MISC",
                     url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
                  },
                  {
                     name: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
                     refsource: "CONFIRM",
                     url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
                  },
               ],
            },
            source: {
               advisory: "GHSA-5955-9wpr-37jh",
               discovery: "UNKNOWN",
            },
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2021-37713",
      datePublished: "2021-08-31T16:50:09",
      dateReserved: "2021-07-29T00:00:00",
      dateUpdated: "2024-08-04T01:23:01.533Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
}

cve-2021-37701

Vulnerability from cvelistv5

Published

2021-08-31 00:00

Modified

2024-08-04 01:23

Severity ?

8.2 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Summary

The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.

References

▼	URL	Tags
	https://www.npmjs.com/package/tar
	https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc
	https://www.oracle.com/security-alerts/cpuoct2021.html
	https://www.debian.org/security/2021/dsa-5008	vendor-advisory
	https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
	https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html	mailing-list

Impacted products

	Vendor	Product	Version
	npm	node-tar	Version: < 4.4.16 Version: >= 5.0.0, < 5.0.8 Version: >= 6.0.0, < 6.1.7

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-04T01:23:01.526Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://www.npmjs.com/package/tar",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
               },
               {
                  name: "DSA-5008",
                  tags: [
                     "vendor-advisory",
                     "x_transferred",
                  ],
                  url: "https://www.debian.org/security/2021/dsa-5008",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
               },
               {
                  name: "[debian-lts-announce] 20221212 [SECURITY] [DLA 3237-1] node-tar security update",
                  tags: [
                     "mailing-list",
                     "x_transferred",
                  ],
                  url: "https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "node-tar",
               vendor: "npm",
               versions: [
                  {
                     status: "affected",
                     version: "< 4.4.16",
                  },
                  {
                     status: "affected",
                     version: ">= 5.0.0, < 5.0.8",
                  },
                  {
                     status: "affected",
                     version: ">= 6.0.0, < 6.1.7",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "The npm package \"tar\" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\\` and `/` characters as path separators, however `\\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-22",
                     description: "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
            {
               descriptions: [
                  {
                     cweId: "CWE-59",
                     description: "CWE-59: Improper Link Resolution Before File Access ('Link Following')",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-12-12T00:00:00",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               url: "https://www.npmjs.com/package/tar",
            },
            {
               url: "https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc",
            },
            {
               url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
            },
            {
               name: "DSA-5008",
               tags: [
                  "vendor-advisory",
               ],
               url: "https://www.debian.org/security/2021/dsa-5008",
            },
            {
               url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
            },
            {
               name: "[debian-lts-announce] 20221212 [SECURITY] [DLA 3237-1] node-tar security update",
               tags: [
                  "mailing-list",
               ],
               url: "https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html",
            },
         ],
         source: {
            advisory: "GHSA-9r2w-394v-53qc",
            discovery: "UNKNOWN",
         },
         title: "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links",
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2021-37701",
      datePublished: "2021-08-31T00:00:00",
      dateReserved: "2021-07-29T00:00:00",
      dateUpdated: "2024-08-04T01:23:01.526Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
}

cve-2021-22960

Vulnerability from cvelistv5

Published

2021-11-03 19:22

Modified

2024-08-03 18:58

Severity ?

Summary

The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions.

References

▼	URL	Tags
	https://hackerone.com/reports/1238099	x_refsource_MISC
	https://www.oracle.com/security-alerts/cpujan2022.html	x_refsource_MISC
	https://www.debian.org/security/2022/dsa-5170	vendor-advisory, x_refsource_DEBIAN

Impacted products

	Vendor	Product	Version
	n/a	https://github.com/nodejs/llhttp	Version: Fixed in v2.1.4 and v6.0.6

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-03T18:58:26.117Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://hackerone.com/reports/1238099",
               },
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.oracle.com/security-alerts/cpujan2022.html",
               },
               {
                  name: "DSA-5170",
                  tags: [
                     "vendor-advisory",
                     "x_refsource_DEBIAN",
                     "x_transferred",
                  ],
                  url: "https://www.debian.org/security/2022/dsa-5170",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "https://github.com/nodejs/llhttp",
               vendor: "n/a",
               versions: [
                  {
                     status: "affected",
                     version: "Fixed in v2.1.4 and v6.0.6",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions.",
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-444",
                     description: "HTTP Request Smuggling (CWE-444)",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-06-28T10:06:19",
            orgId: "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
            shortName: "hackerone",
         },
         references: [
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://hackerone.com/reports/1238099",
            },
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.oracle.com/security-alerts/cpujan2022.html",
            },
            {
               name: "DSA-5170",
               tags: [
                  "vendor-advisory",
                  "x_refsource_DEBIAN",
               ],
               url: "https://www.debian.org/security/2022/dsa-5170",
            },
         ],
         x_legacyV4Record: {
            CVE_data_meta: {
               ASSIGNER: "support@hackerone.com",
               ID: "CVE-2021-22960",
               STATE: "PUBLIC",
            },
            affects: {
               vendor: {
                  vendor_data: [
                     {
                        product: {
                           product_data: [
                              {
                                 product_name: "https://github.com/nodejs/llhttp",
                                 version: {
                                    version_data: [
                                       {
                                          version_value: "Fixed in v2.1.4 and v6.0.6",
                                       },
                                    ],
                                 },
                              },
                           ],
                        },
                        vendor_name: "n/a",
                     },
                  ],
               },
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "eng",
                     value: "The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "eng",
                           value: "HTTP Request Smuggling (CWE-444)",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://hackerone.com/reports/1238099",
                     refsource: "MISC",
                     url: "https://hackerone.com/reports/1238099",
                  },
                  {
                     name: "https://www.oracle.com/security-alerts/cpujan2022.html",
                     refsource: "MISC",
                     url: "https://www.oracle.com/security-alerts/cpujan2022.html",
                  },
                  {
                     name: "DSA-5170",
                     refsource: "DEBIAN",
                     url: "https://www.debian.org/security/2022/dsa-5170",
                  },
               ],
            },
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
      assignerShortName: "hackerone",
      cveId: "CVE-2021-22960",
      datePublished: "2021-11-03T19:22:42",
      dateReserved: "2021-01-06T00:00:00",
      dateUpdated: "2024-08-03T18:58:26.117Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
}

cve-2021-22959

Vulnerability from cvelistv5

Published

2021-11-15 14:45

Modified

2024-08-03 18:58

Severity ?

Summary

The parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6.

References

▼	URL	Tags
	https://hackerone.com/reports/1238709	x_refsource_MISC
	https://www.oracle.com/security-alerts/cpujan2022.html	x_refsource_MISC
	https://www.debian.org/security/2022/dsa-5170	vendor-advisory, x_refsource_DEBIAN

Impacted products

	Vendor	Product	Version
	n/a	https://github.com/nodejs/llhttp	Version: Fixed in llhttp v2.1.4 and v6.0.6

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-03T18:58:26.156Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://hackerone.com/reports/1238709",
               },
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.oracle.com/security-alerts/cpujan2022.html",
               },
               {
                  name: "DSA-5170",
                  tags: [
                     "vendor-advisory",
                     "x_refsource_DEBIAN",
                     "x_transferred",
                  ],
                  url: "https://www.debian.org/security/2022/dsa-5170",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "https://github.com/nodejs/llhttp",
               vendor: "n/a",
               versions: [
                  {
                     status: "affected",
                     version: "Fixed in llhttp v2.1.4 and v6.0.6",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "The parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6.",
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-444",
                     description: "HTTP Request Smuggling (CWE-444)",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-06-28T10:06:15",
            orgId: "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
            shortName: "hackerone",
         },
         references: [
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://hackerone.com/reports/1238709",
            },
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.oracle.com/security-alerts/cpujan2022.html",
            },
            {
               name: "DSA-5170",
               tags: [
                  "vendor-advisory",
                  "x_refsource_DEBIAN",
               ],
               url: "https://www.debian.org/security/2022/dsa-5170",
            },
         ],
         x_legacyV4Record: {
            CVE_data_meta: {
               ASSIGNER: "support@hackerone.com",
               ID: "CVE-2021-22959",
               STATE: "PUBLIC",
            },
            affects: {
               vendor: {
                  vendor_data: [
                     {
                        product: {
                           product_data: [
                              {
                                 product_name: "https://github.com/nodejs/llhttp",
                                 version: {
                                    version_data: [
                                       {
                                          version_value: "Fixed in llhttp v2.1.4 and v6.0.6",
                                       },
                                    ],
                                 },
                              },
                           ],
                        },
                        vendor_name: "n/a",
                     },
                  ],
               },
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "eng",
                     value: "The parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "eng",
                           value: "HTTP Request Smuggling (CWE-444)",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://hackerone.com/reports/1238709",
                     refsource: "MISC",
                     url: "https://hackerone.com/reports/1238709",
                  },
                  {
                     name: "https://www.oracle.com/security-alerts/cpujan2022.html",
                     refsource: "MISC",
                     url: "https://www.oracle.com/security-alerts/cpujan2022.html",
                  },
                  {
                     name: "DSA-5170",
                     refsource: "DEBIAN",
                     url: "https://www.debian.org/security/2022/dsa-5170",
                  },
               ],
            },
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
      assignerShortName: "hackerone",
      cveId: "CVE-2021-22959",
      datePublished: "2021-11-15T14:45:16",
      dateReserved: "2021-01-06T00:00:00",
      dateUpdated: "2024-08-03T18:58:26.156Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
}

cve-2021-37712

Vulnerability from cvelistv5

Published

2021-08-31 00:00

Modified

2024-08-04 01:23

Severity ?

8.2 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Summary

The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.

References

▼	URL	Tags
	https://www.npmjs.com/package/tar
	https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p
	https://www.oracle.com/security-alerts/cpuoct2021.html
	https://www.debian.org/security/2021/dsa-5008	vendor-advisory
	https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
	https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html	mailing-list

Impacted products

	Vendor	Product	Version
	npm	node-tar	Version: < 4.4.18 Version: >= 5.0.0, < 5.0.10 Version: >= 6.0.0, < 6.1.9

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-04T01:23:01.507Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://www.npmjs.com/package/tar",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
               },
               {
                  name: "DSA-5008",
                  tags: [
                     "vendor-advisory",
                     "x_transferred",
                  ],
                  url: "https://www.debian.org/security/2021/dsa-5008",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
               },
               {
                  name: "[debian-lts-announce] 20221212 [SECURITY] [DLA 3237-1] node-tar security update",
                  tags: [
                     "mailing-list",
                     "x_transferred",
                  ],
                  url: "https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "node-tar",
               vendor: "npm",
               versions: [
                  {
                     status: "affected",
                     version: "< 4.4.18",
                  },
                  {
                     status: "affected",
                     version: ">= 5.0.0, < 5.0.10",
                  },
                  {
                     status: "affected",
                     version: ">= 6.0.0, < 6.1.9",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 \"short path\" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-22",
                     description: "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
            {
               descriptions: [
                  {
                     cweId: "CWE-59",
                     description: "CWE-59: Improper Link Resolution Before File Access ('Link Following')",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-12-12T00:00:00",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               url: "https://www.npmjs.com/package/tar",
            },
            {
               url: "https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p",
            },
            {
               url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
            },
            {
               name: "DSA-5008",
               tags: [
                  "vendor-advisory",
               ],
               url: "https://www.debian.org/security/2021/dsa-5008",
            },
            {
               url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
            },
            {
               name: "[debian-lts-announce] 20221212 [SECURITY] [DLA 3237-1] node-tar security update",
               tags: [
                  "mailing-list",
               ],
               url: "https://lists.debian.org/debian-lts-announce/2022/12/msg00023.html",
            },
         ],
         source: {
            advisory: "GHSA-qq89-hq3f-393p",
            discovery: "UNKNOWN",
         },
         title: "Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links",
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2021-37712",
      datePublished: "2021-08-31T00:00:00",
      dateReserved: "2021-07-29T00:00:00",
      dateUpdated: "2024-08-04T01:23:01.507Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
}

cve-2021-39134

Vulnerability from cvelistv5

Published

2021-08-31 16:55

Modified

2024-08-04 01:58

Severity ?

8.2 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Summary

`@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. When multiple dependencies differ only in the case of their name, Arborist's internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. For example, a package `pwn-a` could define a dependency in their `package.json` file such as `"foo": "file:/some/path"`. Another package, `pwn-b` could define a dependency such as `FOO: "file:foo.tgz"`. On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed. Anyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above.

References

▼	URL	Tags
	https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc	x_refsource_CONFIRM
	https://www.npmjs.com/package/%40npmcli/arborist	x_refsource_MISC
	https://www.oracle.com/security-alerts/cpuoct2021.html	x_refsource_MISC
	https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf	x_refsource_CONFIRM

Impacted products

	Vendor	Product	Version
	npm	arborist	Version: < 2.8.2

Show details on NVD website

JSON

To clipboard

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-04T01:58:17.840Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_refsource_CONFIRM",
                     "x_transferred",
                  ],
                  url: "https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc",
               },
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.npmjs.com/package/%40npmcli/arborist",
               },
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
               },
               {
                  tags: [
                     "x_refsource_CONFIRM",
                     "x_transferred",
                  ],
                  url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "arborist",
               vendor: "npm",
               versions: [
                  {
                     status: "affected",
                     version: "< 2.8.2",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "`@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. When multiple dependencies differ only in the case of their name, Arborist's internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. For example, a package `pwn-a` could define a dependency in their `package.json` file such as `\"foo\": \"file:/some/path\"`. Another package, `pwn-b` could define a dependency such as `FOO: \"file:foo.tgz\"`. On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed. Anyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-61",
                     description: "CWE-61: UNIX Symbolic Link (Symlink) Following",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-03-08T14:07:47",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc",
            },
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.npmjs.com/package/%40npmcli/arborist",
            },
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
            },
            {
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
            },
         ],
         source: {
            advisory: "GHSA-2h3h-q99f-3fhc",
            discovery: "UNKNOWN",
         },
         title: "UNIX Symbolic Link (Symlink) Following in @npmcli/arborist",
         x_legacyV4Record: {
            CVE_data_meta: {
               ASSIGNER: "security-advisories@github.com",
               ID: "CVE-2021-39134",
               STATE: "PUBLIC",
               TITLE: "UNIX Symbolic Link (Symlink) Following in @npmcli/arborist",
            },
            affects: {
               vendor: {
                  vendor_data: [
                     {
                        product: {
                           product_data: [
                              {
                                 product_name: "arborist",
                                 version: {
                                    version_data: [
                                       {
                                          version_value: "< 2.8.2",
                                       },
                                    ],
                                 },
                              },
                           ],
                        },
                        vendor_name: "npm",
                     },
                  ],
               },
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "eng",
                     value: "`@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. When multiple dependencies differ only in the case of their name, Arborist's internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. For example, a package `pwn-a` could define a dependency in their `package.json` file such as `\"foo\": \"file:/some/path\"`. Another package, `pwn-b` could define a dependency such as `FOO: \"file:foo.tgz\"`. On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed. Anyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above.",
                  },
               ],
            },
            impact: {
               cvss: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 8.2,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "NONE",
                  scope: "CHANGED",
                  userInteraction: "REQUIRED",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
                  version: "3.1",
               },
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "eng",
                           value: "CWE-61: UNIX Symbolic Link (Symlink) Following",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc",
                     refsource: "CONFIRM",
                     url: "https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc",
                  },
                  {
                     name: "https://www.npmjs.com/package/@npmcli/arborist",
                     refsource: "MISC",
                     url: "https://www.npmjs.com/package/@npmcli/arborist",
                  },
                  {
                     name: "https://www.oracle.com/security-alerts/cpuoct2021.html",
                     refsource: "MISC",
                     url: "https://www.oracle.com/security-alerts/cpuoct2021.html",
                  },
                  {
                     name: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
                     refsource: "CONFIRM",
                     url: "https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf",
                  },
               ],
            },
            source: {
               advisory: "GHSA-2h3h-q99f-3fhc",
               discovery: "UNKNOWN",
            },
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2021-39134",
      datePublished: "2021-08-31T16:55:11",
      dateReserved: "2021-08-16T00:00:00",
      dateUpdated: "2024-08-04T01:58:17.840Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
}

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.

Action not permitted

Vulnerability from csaf_opensuse

cve-2021-39135

Vulnerability from cvelistv5

cve-2021-37713

Vulnerability from cvelistv5

cve-2021-37701

Vulnerability from cvelistv5

cve-2021-22960

Vulnerability from cvelistv5

cve-2021-22959

Vulnerability from cvelistv5

cve-2021-37712

Vulnerability from cvelistv5

cve-2021-39134

Vulnerability from cvelistv5

Tags

Sightings

Nomenclature