Every CVE Search/ Get API key

CVE-2021-37713

Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization

8.2 HighFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
None
User interaction
Required

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
None

Exploit likelihood

1.27%Up 0.2 points since Sep 1, 2021
90%50%10%1%

What each source reports

CVE List Score used 8.2

Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization

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.

Record
CVE-2021-37713
CVSS 3.1
8.2 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Weakness
CWE-22
Updated
2026-11-02
EUVDEUVD-2021-1573 8.2

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.

Record
EUVD-2021-1573
CVSS 3.1
8.2 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Updated
2026-11-03
GitHub AdvisoriesGHSA-5955-9wpr-37jh 8.2

Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization

Impact

Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution

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.

Patches

4.4.18 || 5.0.10 || 6.1.9

Workarounds

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.

Fix

The fixed versions strip path roots from all paths prior to being resolved against the extraction target folder, even if such paths are not "absolute".

Additionally, a path starting with a drive letter and then two dots, like c:../, would bypass the check for .. path portions. This is checked properly in the patched versions.

Finally, a defense in depth check is added, such that if the entry.absolute is outside of the extraction taret, and we are not in preservePaths:true mode, a warning is raised on that entry, and it is skipped. Currently, it is believed that this check is redundant, but it did catch some oversights in development.

Record
GHSA-5955-9wpr-37jh
CVSS 3.1
8.2 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Weakness
CWE-22
Updated
2026-11-02
NVD 8.2

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.

Record
CVE-2021-37713
CVSS 3.1
8.2 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CVSS 3.1
8.6 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CVSS 2.0
4.4 MediumAV:L/AC:M/Au:N/C:P/I:P/A:P
Weakness
CWE-22
Updated
2026-11-02
OSVALPINE-CVE-2021-37713 8.6

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.

Record
ALPINE-CVE-2021-37713
CVSS 3.1
8.6 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Updated
2026-11-02
OSVBELL-CVE-2021-37713 8.6

CVE-2021-37713 does not affect BellSoft software

Record
BELL-CVE-2021-37713
CVSS 3.1
8.6 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Updated
2026-11-02
Show 20 moreShow less
OSV 8.6

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.

Record
CVE-2021-37713
CVSS 3.1
8.6 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Updated
2026-11-02
OSVGHSA-5955-9wpr-37jh 8.2

Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization

Impact

Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution

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.

Patches

4.4.18 || 5.0.10 || 6.1.9

Workarounds

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.

Fix

The fixed versions strip path roots from all paths prior to being resolved against the extraction target folder, even if such paths are not "absolute".

Additionally, a path starting with a drive letter and then two dots, like c:../, would bypass the check for .. path portions. This is checked properly in the patched versions.

Finally, a defense in depth check is added, such that if the entry.absolute is outside of the extraction taret, and we are not in preservePaths:true mode, a warning is raised on that entry, and it is skipped. Currently, it is believed that this check is redundant, but it did catch some oversights in development.

Record
GHSA-5955-9wpr-37jh
CVSS 3.1
8.2 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Weakness
CWE-22
Updated
2026-11-02
OSVCLSA-2026-1773188129 No score

TuxCare security update for tar (7 CVEs)

TuxCare rebuilt tar to address 7 CVEs. Fixed in 2.2.2-tuxcare.1.

Record
CLSA-2026-1773188129
Updated
2026-11-02
OSVCLSA-2026-1773620217 No score

TuxCare security update for tar (4 CVEs)

TuxCare rebuilt tar to address 4 CVEs. Fixed in 1.0.3-tuxcare.1.

Record
CLSA-2026-1773620217
Updated
2026-11-02
OSVCLSA-2026-1774484514 No score

TuxCare security update for tar (5 CVEs)

TuxCare rebuilt tar to address 5 CVEs. Fixed in 2.1.1-tuxcare.1.

Record
CLSA-2026-1774484514
Updated
2026-11-02
OSVCLSA-2026-1775176107 No score

TuxCare security update for tar (2 CVEs)

TuxCare rebuilt tar to address 2 CVEs. Fixed in 6.0.2-tuxcare.3.

Record
CLSA-2026-1775176107
Updated
2026-11-02
OSVCLSA-2026-1792164662 No score

TuxCare security update for tar (8 CVEs)

TuxCare rebuilt tar to address 8 CVEs. Fixed in 6.1.6-tuxcare.1.

Record
CLSA-2026-1792164662
Updated
2026-11-02
OSVCLSA-2026-1792369404 No score

TuxCare security update for tar (9 CVEs)

TuxCare rebuilt tar to address 9 CVEs. Fixed in 6.1.0-tuxcare.2.

Record
CLSA-2026-1792369404
Updated
2026-11-02
OSVCLSA-2026-1793790160 No score

TuxCare security update for tar (1 CVE)

TuxCare rebuilt tar to address 1 CVE. Fixed in 4.4.6-tuxcare.1.

Record
CLSA-2026-1793790160
Updated
2026-11-04
OSVMGASA-2021-0463 No score

Updated nodejs packages fix security vulnerability

Multiple security fixes for nodejs. See references for details

Record
MGASA-2021-0463
Updated
2026-11-02
OSVopenSUSE-SU-2021:1552-1 No score

Security update for nodejs14

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

  • deps: update llhttp to 2.1.4

    • HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
    • HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

  • buffer:

    • introduce Blob
    • add base64url encoding option
  • child_process:

    • allow options.cwd receive a URL
    • add timeout to spawn and fork
    • allow promisified exec to be cancel
    • add 'overlapped' stdio flag
  • dns: add 'tries' option to Resolve options

  • fs:

    • allow empty string for temp directory prefix
    • allow no-params fsPromises fileHandle read
    • add support for async iterators to fsPromises.writeFile
  • http2: add support for sensitive headers

  • process: add 'worker' event

  • tls: allow reading data into a static buffer

  • worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6

  • deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)

This update was imported from the SUSE:SLE-15-SP2:Update update project.

Record
openSUSE-SU-2021:1552-1
Updated
2026-11-02
OSVopenSUSE-SU-2021:1574-1 No score

Security update for nodejs12

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

This update was imported from the SUSE:SLE-15-SP2:Update update project.

Record
openSUSE-SU-2021:1574-1
Updated
2026-11-02
OSVopenSUSE-SU-2021:3940-1 No score

Security update for nodejs12

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).
Record
openSUSE-SU-2021:3940-1
Updated
2026-11-02
OSVopenSUSE-SU-2021:3964-1 No score

Security update for nodejs14

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

  • deps: update llhttp to 2.1.4

    • HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
    • HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

  • buffer:

    • introduce Blob
    • add base64url encoding option
  • child_process:

    • allow options.cwd receive a URL
    • add timeout to spawn and fork
    • allow promisified exec to be cancel
    • add 'overlapped' stdio flag
  • dns: add 'tries' option to Resolve options

  • fs:

    • allow empty string for temp directory prefix
    • allow no-params fsPromises fileHandle read
    • add support for async iterators to fsPromises.writeFile
  • http2: add support for sensitive headers

  • process: add 'worker' event

  • tls: allow reading data into a static buffer

  • worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6

  • deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)
Record
openSUSE-SU-2021:3964-1
Updated
2026-11-02
OSVopenSUSE-SU-2024:11616-1 No score

nodejs14-14.18.1-1.1 on GA media

These are all security issues fixed in the nodejs14-14.18.1-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2024:11616-1
Updated
2026-11-02
OSVROOT-APP-NPM-CVE-2021-37713 No score

CVE-2021-37713 in tar - Patched by Root

Root has patched CVE-2021-37713 in the tar package for Root:npm. Multiple fixed versions available.

Record
ROOT-APP-NPM-CVE-2021-37713
Updated
2026-11-02
OSVSUSE-SU-2021:3886-1 No score

Security update for nodejs14

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

  • deps: update llhttp to 2.1.4

Security fixes:

  • HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
  • HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

  • buffer:

    • introduce Blob
    • add base64url encoding option
  • child_process:

    • allow options.cwd receive a URL
    • add timeout to spawn and fork
    • allow promisified exec to be cancel
    • add 'overlapped' stdio flag
  • dns: add 'tries' option to Resolve options

  • fs:

    • allow empty string for temp directory prefix
    • allow no-params fsPromises fileHandle read
    • add support for async iterators to fsPromises.writeFile
  • http2: add support for sensitive headers

  • process: add 'worker' event

  • tls: allow reading data into a static buffer

  • worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6:

  • deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)
Record
SUSE-SU-2021:3886-1
Updated
2026-11-02
OSVSUSE-SU-2021:3940-1 No score

Security update for nodejs12

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).
Record
SUSE-SU-2021:3940-1
Updated
2026-11-02
OSVSUSE-SU-2021:3964-1 No score

Security update for nodejs14

This update for nodejs14 fixes the following issues:

nodejs14 was updated to 14.18.1:

  • deps: update llhttp to 2.1.4

    • HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)
    • HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)

Changes in 14.18.0:

  • buffer:

    • introduce Blob
    • add base64url encoding option
  • child_process:

    • allow options.cwd receive a URL
    • add timeout to spawn and fork
    • allow promisified exec to be cancel
    • add 'overlapped' stdio flag
  • dns: add 'tries' option to Resolve options

  • fs:

    • allow empty string for temp directory prefix
    • allow no-params fsPromises fileHandle read
    • add support for async iterators to fsPromises.writeFile
  • http2: add support for sensitive headers

  • process: add 'worker' event

  • tls: allow reading data into a static buffer

  • worker: add setEnvironmentData/getEnvironmentData

Changes in 14.17.6

  • deps: upgrade npm to 6.14.15 which fixes a number of security issues (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712, bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134, bsc#1190053, CVE-2021-39135)
Record
SUSE-SU-2021:3964-1
Updated
2026-11-02
OSVSUSE-SU-2022:0101-1 No score

Security update for nodejs12

This update for nodejs12 fixes the following issues:

  • CVE-2021-44531: Fixed improper handling of URI Subject Alternative Names (bsc#1194511).
  • CVE-2021-44532: Fixed certificate Verification Bypass via String Injection (bsc#1194512).
  • CVE-2021-44533: Fixed incorrect handling of certificate subject and issuer fields (bsc#1194513).
  • CVE-2022-21824: Fixed prototype pollution via console.table properties (bsc#1194514).
  • 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 vulnerability in nodejs-tar (bsc#1190057).
  • CVE-2021-37712: Fixed arbitrary file creation and overwrite vulnerability in nodejs-tar (bsc#1190056).
  • CVE-2021-37713: Fixed arbitrary file creation/overwrite and arbitrary code execution vulnerability in nodejs-tar (bsc#1190055).
  • CVE-2021-39134: Fixed symlink following vulnerability in nodejs-arborist (bsc#1190054).
  • CVE-2021-39135: Fixed symlink following vulnerability in nodejs-arborist (bsc#1190053).
Record
SUSE-SU-2022:0101-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
tar
npm
before 4.4.18
4.4.18
tar
npm
5.0.0 up to 5.0.10
5.0.10
tar
npm
6.0.0 up to 6.1.9
6.1.9
nodejs
Alpine:v3.11
before 12.22.6-r0
12.22.6-r0
nodejs
Alpine:v3.12
before 12.22.6-r0
12.22.6-r0
nodejs
Alpine:v3.13
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.14
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.15
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.16
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.17
before 14.17.6-r0
14.17.6-r0
Show 28 moreShow less
Affected packages
PackageAffectedFixed
nodejs
Alpine:v3.18
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.19
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.20
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.21
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.22
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.23
before 14.17.6-r0
14.17.6-r0
nodejs
Alpine:v3.24
before 14.17.6-r0
14.17.6-r0
tar
TuxCare:npm
From an advisory covering 7 CVEs
2.2.2-tuxcare.0 up to 2.2.2-tuxcare.1, plus listed versions
2.2.2
2.2.2-tuxcare.1
tar
TuxCare:npm
From an advisory covering 4 CVEs
1.0.3-tuxcare.0 up to 1.0.3-tuxcare.1, plus listed versions
1.0.3
1.0.3-tuxcare.1
tar
TuxCare:npm
From an advisory covering 5 CVEs
2.1.1-tuxcare.0 up to 2.1.1-tuxcare.1, plus listed versions
2.1.1
2.1.1-tuxcare.1
tar
TuxCare:npm
From an advisory covering 2 CVEs
6.0.2-tuxcare.0 up to 6.0.2-tuxcare.3, plus listed versions
6.0.26.0.2-tuxcare.16.0.2-tuxcare.2
6.0.2-tuxcare.3
tar
TuxCare:npm
From an advisory covering 8 CVEs
6.1.6-tuxcare.0 up to 6.1.6-tuxcare.1, plus listed versions
6.1.6
6.1.6-tuxcare.1
tar
TuxCare:npm
From an advisory covering 9 CVEs
6.1.0-tuxcare.0 up to 6.1.0-tuxcare.2, plus listed versions
6.1.06.1.0-tuxcare.1
6.1.0-tuxcare.2
tar
TuxCare:npm
4.4.6-tuxcare.0 up to 4.4.6-tuxcare.1, plus listed versions
4.4.6
4.4.6-tuxcare.1
nodejs
Mageia:8
From an advisory covering 9 CVEs
before 14.17.6-1.mga8
14.17.6-1.mga8
tar
Root:npm
before 4.4.13-aikido.1
4.4.13-aikido.1
@rootio/tar
Root:npm
before 4.4.13-root.io.1
4.4.13-root.io.1
nodejs14
SUSE:Linux Enterprise Module for Web and Scripting 12
From an advisory covering 7 CVEs
before 14.18.1-6.18.2
14.18.1-6.18.2
nodejs12
SUSE:Linux Enterprise Module for Web and Scripting 15 SP2
From an advisory covering 7 CVEs
before 12.22.7-4.22.1
12.22.7-4.22.1
nodejs12
SUSE:Linux Enterprise Module for Web and Scripting 15 SP3
From an advisory covering 7 CVEs
before 12.22.7-4.22.1
12.22.7-4.22.1
nodejs14
SUSE:Linux Enterprise Module for Web and Scripting 15 SP2
From an advisory covering 7 CVEs
before 14.18.1-15.21.2
14.18.1-15.21.2
nodejs14
SUSE:Linux Enterprise Module for Web and Scripting 15 SP3
From an advisory covering 7 CVEs
before 14.18.1-15.21.2
14.18.1-15.21.2
nodejs12
SUSE:Linux Enterprise Module for Web and Scripting 12
From an advisory covering 11 CVEs
before 12.22.9-1.38.1
12.22.9-1.38.1
nodejs14
openSUSE:Leap 15.2
From an advisory covering 7 CVEs
before 14.18.1-lp152.17.1
14.18.1-lp152.17.1
nodejs12
openSUSE:Leap 15.2
From an advisory covering 7 CVEs
before 12.22.7-lp152.3.21.1
12.22.7-lp152.3.21.1
nodejs12
openSUSE:Leap 15.3
From an advisory covering 7 CVEs
before 12.22.7-4.22.1
12.22.7-4.22.1
nodejs14
openSUSE:Leap 15.3
From an advisory covering 7 CVEs
before 14.18.1-15.21.2
14.18.1-15.21.2
nodejs14
openSUSE:Tumbleweed
From an advisory covering 5 CVEs
before 14.18.1-1.1
14.18.1-1.1

History

History
RecordedChangedSources
affected
affected, aliases, factsOSV
aliases, productsEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2021-37713 is a high vulnerability (CVSS 8.2) in Isaacs Node-tar, published August 31, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.27%, the 70th percentile. Fixed in tar 4.4.18.

References

Show 42 moreShow less
MoveEnter Open