CVE-2021-32803
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
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
What each source reports
CVE List Score used
8.2
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
- Record
CVE-2021-32803- CVSS 3.1
- 8.2 High
CVSS: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-1856
8.2
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
- Record
EUVD-2021-1856- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-r628-mhmh-qjhw
8.2
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur.
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.
This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
Patches
3.2.3 || 4.4.15 || 5.0.7 || 6.1.2
Workarounds
Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
Users are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.
- Record
GHSA-r628-mhmh-qjhw- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - Weakness
- CWE-22, CWE-23, CWE-59
- Updated
- 2026-11-02
NVD
8.2
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
- Record
CVE-2021-32803- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - CVSS 2.0
- 5.8 Medium
AV:N/AC:M/Au:N/C:N/I:P/A:P - Weakness
- CWE-22, CWE-59
- Updated
- 2026-11-02
OSVALPINE-CVE-2021-32803
8.1
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
- Record
ALPINE-CVE-2021-32803- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - Updated
- 2026-11-02
OSVBELL-CVE-2021-32803
8.1
CVE-2021-32803 does not affect BellSoft software
- Record
BELL-CVE-2021-32803- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - Updated
- 2026-11-02
Show 31 moreShow less
OSV
8.1
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
- Record
CVE-2021-32803- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2021-32803
8.1
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
- Record
DEBIAN-CVE-2021-32803- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-r628-mhmh-qjhw
8.2
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur.
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.
This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
Patches
3.2.3 || 4.4.15 || 5.0.7 || 6.1.2
Workarounds
Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links.
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
Users are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves.
- Record
GHSA-r628-mhmh-qjhw- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - Weakness
- CWE-22, CWE-23, CWE-59
- Updated
- 2026-11-02
OSVRHSA-2021:3280
9.8
Red Hat Security Advisory: rh-nodejs14-nodejs and rh-nodejs14-nodejs-nodemon security update
- Record
RHSA-2021:3280- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2021:3281
9.8
Red Hat Security Advisory: rh-nodejs12-nodejs and rh-nodejs12-nodejs-nodemon security update
- Record
RHSA-2021:3281- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2021:3623
9.8
Red Hat Security Advisory: nodejs:12 security and bug fix update
- Record
RHSA-2021:3623- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2021:3638
9.8
Red Hat Security Advisory: nodejs:12 security and bug fix update
- Record
RHSA-2021:3638- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2021:3639
9.8
Red Hat Security Advisory: nodejs:12 security and bug fix update
- Record
RHSA-2021:3639- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRHSA-2021:3666
9.8
Red Hat Security Advisory: nodejs:14 security and bug fix update
- Record
RHSA-2021:3666- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRLSA-2021:3623
9.8
Important: nodejs:12 security and bug fix update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930)
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22940)
-
c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)
-
nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)
-
nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite (CVE-2021-32803)
-
nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite (CVE-2021-32804)
-
nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)
-
nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Bug Fix(es):
- nodejs:12/nodejs: Make FIPS options always available (BZ#1993927)
- Record
RLSA-2021:3623- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVRLSA-2021:3666
9.8
Important: nodejs:14 security and bug fix update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930)
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22940)
-
c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)
-
nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)
-
nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite (CVE-2021-32803)
-
nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite (CVE-2021-32804)
-
nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)
-
nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Bug Fix(es):
- nodejs:14/nodejs: Make FIPS options always available (BZ#1993924)
- Record
RLSA-2021:3666- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2021-32803
8.2
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. 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. This order of operations resulted in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. 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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
- Record
UBUNTU-CVE-2021-32803- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - Updated
- 2026-11-02
OSVALSA-2021:3623 No score
Important: nodejs:12 security and bug fix update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930)
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22940)
-
c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)
-
nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)
-
nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite (CVE-2021-32803)
-
nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite (CVE-2021-32804)
-
nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)
-
nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Bug Fix(es):
- nodejs:12/nodejs: Make FIPS options always available (BZ#1993927)
- Record
ALSA-2021:3623- Updated
- 2026-11-02
OSVALSA-2021:3666 No score
Important: nodejs:14 security and bug fix update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22930)
-
nodejs: Use-after-free on close http2 on stream canceling (CVE-2021-22940)
-
c-ares: Missing input validation of host names may lead to domain hijacking (CVE-2021-3672)
-
nodejs: Improper handling of untypical characters in domain names (CVE-2021-22931)
-
nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwrite (CVE-2021-32803)
-
nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwrite (CVE-2021-32804)
-
nodejs: Incomplete validation of tls rejectUnauthorized parameter (CVE-2021-22939)
-
nodejs-path-parse: ReDoS via splitDeviceRe, splitTailRe and splitPathRe (CVE-2021-23343)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Bug Fix(es):
- nodejs:14/nodejs: Make FIPS options always available (BZ#1993924)
- Record
ALSA-2021:3666- Updated
- 2026-11-02
OSVCLSA-2026-1775176089 No score
TuxCare security update for tar (1 CVE)
TuxCare rebuilt tar to address 1 CVE. Fixed in 6.0.2-tuxcare.1.
- Record
CLSA-2026-1775176089- Updated
- 2026-11-02
OSVCLSA-2026-1787823934 No score
TuxCare security update for tar (4 CVEs)
TuxCare rebuilt tar to address 4 CVEs. Fixed in 6.0.2-tuxcare.1.
- Record
CLSA-2026-1787823934- Updated
- 2026-11-02
OSVCLSA-2026-1792164455 No score
TuxCare security update for tar (1 CVE)
TuxCare rebuilt tar to address 1 CVE. Fixed in 6.1.0-tuxcare.1.
- Record
CLSA-2026-1792164455- Updated
- 2026-11-02
OSVMGASA-2022-0103 No score
Updated nodejs-tar packages fix security vulnerability
Untrusted tar file to symlink into an arbitrary location allowing file overwrites. (CVE-2021-37712)
Arbitrary file creation/overwrite and arbitrary code execution. (CVE-2021-37701)
Arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. (CVE-2021-32803)
Arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization (CVE-2021-32804)
- Record
MGASA-2022-0103- Updated
- 2026-11-02
OSVopenSUSE-SU-2022:0657-1 No score
Security update for nodejs12
This update for nodejs12 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
openSUSE-SU-2022:0657-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2022:0704-1 No score
Security update for nodejs8
This update for nodejs8 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
openSUSE-SU-2022:0704-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2022:0715-1 No score
Security update for nodejs14
This update for nodejs14 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
openSUSE-SU-2022:0715-1- Updated
- 2026-11-02
OSVROOT-APP-NPM-CVE-2021-32803 No score
CVE-2021-32803 in tar - Patched by Root
Root has patched CVE-2021-32803 in the tar package for Root:npm. Multiple fixed versions available.
- Record
ROOT-APP-NPM-CVE-2021-32803- Updated
- 2026-11-02
OSVSUSE-SU-2022:0531-1 No score
Security update for nodejs12
This update for nodejs12 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
SUSE-SU-2022:0531-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:0563-1 No score
Security update for nodejs8
This update for nodejs8 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
SUSE-SU-2022:0563-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:0569-1 No score
Security update for nodejs14
This update for nodejs14 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
SUSE-SU-2022:0569-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:0570-1 No score
Security update for nodejs10
This update for nodejs10 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- CVE-2022-21824: Fixed prototype pollution via console.table (bsc#1194514).
- Record
SUSE-SU-2022:0570-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:0657-1 No score
Security update for nodejs12
This update for nodejs12 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
SUSE-SU-2022:0657-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:0704-1 No score
Security update for nodejs8
This update for nodejs8 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
SUSE-SU-2022:0704-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:0715-1 No score
Security update for nodejs14
This update for nodejs14 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- Record
SUSE-SU-2022:0715-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:1717-1 No score
Security update for nodejs10
This update for nodejs10 fixes the following issues:
- CVE-2021-23343: Fixed ReDoS via splitDeviceRe, splitTailRe and splitPathRe (bsc#1192153).
- CVE-2021-32803: Fixed insufficient symlink protection in node-tar allowing arbitrary file creation and overwrite (bsc#1191963).
- CVE-2021-32804: Fixed insufficient absolute path sanitization in node-tar allowing arbitrary file creation and overwrite (bsc#1191962).
- CVE-2021-3918: Fixed improper controlled modification of object prototype attributes in json-schema (bsc#1192696).
- CVE-2021-3807: Fixed regular expression denial of service (ReDoS) matching ANSI escape codes in node-ansi-regex (bsc#1192154).
- CVE-2022-21824: Fixed prototype pollution via console.table (bsc#1194514).
- CVE-2021-44906: Fixed prototype pollution in npm dependency (bsc#1198247).
- CVE-2021-44907: Fixed insuficient sanitation in npm dependency (bsc#1197283).
- CVE-2022-0235: Fixed passing of cookie data and sensitive headers to different hostnames in node-fetch-npm (bsc#1194819).
- Record
SUSE-SU-2022:1717-1- Updated
- 2026-11-02
OSVUSN-5283-1 No score
node-tar vulnerability
It was discovered that Tar for Node.js did not properly sanitize path inputs. An attacker could possibly use this issue to read arbitrary files, resulting in a directory traversal attack.
- Record
USN-5283-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
tarnpm |
4.0.0 up to 4.4.15 | 4.4.15 |
tarnpm |
5.0.0 up to 5.0.7 | 5.0.7 |
tarnpm |
6.0.0 up to 6.1.2 | 6.1.2 |
tarnpm |
3.0.0 up to 3.2.3 | 3.2.3 |
nodejsAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
nodejsAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module_el8.5.0+85+79a7b441 | 1:12.22.5-1.module_el8.5.0+85+79a7b441 |
nodejs-develAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module_el8.5.0+85+79a7b441 | 1:12.22.5-1.module_el8.5.0+85+79a7b441 |
nodejs-develAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
nodejs-docsAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
nodejs-full-i18nAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module_el8.5.0+85+79a7b441 | 1:12.22.5-1.module_el8.5.0+85+79a7b441 |
Show 161 moreShow less
| Package | Affected | Fixed |
|---|---|---|
nodejs-full-i18nAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 | 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 |
nodejs-nodemonAlmaLinux:8 From an advisory covering 8 CVEs |
before 2.0.3-1.module_el8.4.0+2521+c668cc9f | 2.0.3-1.module_el8.4.0+2521+c668cc9f |
nodejs-packagingAlmaLinux:8 From an advisory covering 8 CVEs |
before 17-3.module_el8.4.0+2224+b07ac28e | 17-3.module_el8.4.0+2224+b07ac28e |
nodejs-packagingAlmaLinux:8 From an advisory covering 8 CVEs |
before 17-3.module_el8.4.0+2521+c668cc9f | 17-3.module_el8.4.0+2521+c668cc9f |
nodejs-packagingAlmaLinux:8 From an advisory covering 8 CVEs |
before 17-3.module_el8.3.0+2023+d2377ea3 | 17-3.module_el8.3.0+2023+d2377ea3 |
npmAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7 | 1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7 |
npmAlmaLinux:8 From an advisory covering 8 CVEs |
before 1:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b441 | 1:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b441 |
nodejs-packagingAlmaLinux:8 From an advisory covering 8 CVEs |
before 23-3.module_el8.5.0+254+b4526b16 | 23-3.module_el8.5.0+254+b4526b16 |
nodejs-packagingAlmaLinux:8 From an advisory covering 8 CVEs |
before 23-3.module_el8.4.0+2522+3bd42762 | 23-3.module_el8.4.0+2522+3bd42762 |
tarTuxCare:npm |
6.0.2-tuxcare.0 up to 6.0.2-tuxcare.1, plus listed versions 6.0.2 |
6.0.2-tuxcare.1 |
tarTuxCare:npm |
6.1.0-tuxcare.0 up to 6.1.0-tuxcare.1, plus listed versions 6.1.0 |
6.1.0-tuxcare.1 |
node-tarDebian:12 |
before 6.1.7+~cs11.3.10-1 | 6.1.7+~cs11.3.10-1 |
node-tarDebian:13 |
before 6.1.7+~cs11.3.10-1 | 6.1.7+~cs11.3.10-1 |
node-tarDebian:14 |
before 6.1.7+~cs11.3.10-1 | 6.1.7+~cs11.3.10-1 |
nodejs-tarMageia:8 From an advisory covering 4 CVEs |
before 6.0.5-1.1.mga8 | 6.0.5-1.1.mga8 |
rh-nodejs14-nodejs-nodemonRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:2.0.3-5.el7 | 0:2.0.3-5.el7 |
rh-nodejs14-nodejsRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:14.17.5-1.el7 | 0:14.17.5-1.el7 |
rh-nodejs14-nodejs-debuginfoRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:14.17.5-1.el7 | 0:14.17.5-1.el7 |
rh-nodejs14-nodejs-develRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:14.17.5-1.el7 | 0:14.17.5-1.el7 |
rh-nodejs14-nodejs-docsRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:14.17.5-1.el7 | 0:14.17.5-1.el7 |
rh-nodejs14-npmRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:6.14.14-14.17.5.1.el7 | 0:6.14.14-14.17.5.1.el7 |
rh-nodejs12-nodejsRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:12.22.5-1.el7 | 0:12.22.5-1.el7 |
rh-nodejs12-nodejs-debuginfoRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:12.22.5-1.el7 | 0:12.22.5-1.el7 |
rh-nodejs12-nodejs-develRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:12.22.5-1.el7 | 0:12.22.5-1.el7 |
rh-nodejs12-nodejs-docsRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:12.22.5-1.el7 | 0:12.22.5-1.el7 |
rh-nodejs12-nodejs-nodemonRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:2.0.3-5.el7 | 0:2.0.3-5.el7 |
rh-nodejs12-npmRed Hat:rhel_software_collections:3::el7 From an advisory covering 10 CVEs |
before 0:6.14.14-12.22.5.1.el7 | 0:6.14.14-12.22.5.1.el7 |
nodejsRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 | 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 |
nodejs-debuginfoRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 | 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 |
nodejs-debugsourceRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 | 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 |
nodejs-develRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 | 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 |
nodejs-docsRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 | 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 |
nodejs-full-i18nRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 | 1:12.22.5-1.module+el8.4.0+12242+af52a4c7 |
nodejs-nodemonRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 0:2.0.3-1.module+el8.4.0+11732+c668cc9f | 0:2.0.3-1.module+el8.4.0+11732+c668cc9f |
nodejs-packagingRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 0:17-3.module+el8.1.0+3369+37ae6a45 | 0:17-3.module+el8.1.0+3369+37ae6a45 |
npmRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:6.14.14-1.12.22.5.1.module+el8.4.0+12242+af52a4c7 | 1:6.14.14-1.12.22.5.1.module+el8.4.0+12242+af52a4c7 |
nodejsRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.2.0+12241+a3db445b | 1:12.22.5-1.module+el8.2.0+12241+a3db445b |
nodejs-debuginfoRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.2.0+12241+a3db445b | 1:12.22.5-1.module+el8.2.0+12241+a3db445b |
nodejs-debugsourceRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.2.0+12241+a3db445b | 1:12.22.5-1.module+el8.2.0+12241+a3db445b |
nodejs-develRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.2.0+12241+a3db445b | 1:12.22.5-1.module+el8.2.0+12241+a3db445b |
nodejs-docsRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.2.0+12241+a3db445b | 1:12.22.5-1.module+el8.2.0+12241+a3db445b |
nodejs-full-i18nRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.2.0+12241+a3db445b | 1:12.22.5-1.module+el8.2.0+12241+a3db445b |
nodejs-nodemonRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 | 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 |
nodejs-packagingRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 0:17-3.module+el8.1.0+3369+37ae6a45 | 0:17-3.module+el8.1.0+3369+37ae6a45 |
npmRed Hat:rhel_eus:8.2::appstream From an advisory covering 11 CVEs |
before 1:6.14.14-1.12.22.5.1.module+el8.2.0+12241+a3db445b | 1:6.14.14-1.12.22.5.1.module+el8.2.0+12241+a3db445b |
nodejsRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.1.0+12238+63fe3aec | 1:12.22.5-1.module+el8.1.0+12238+63fe3aec |
nodejs-debuginfoRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.1.0+12238+63fe3aec | 1:12.22.5-1.module+el8.1.0+12238+63fe3aec |
nodejs-debugsourceRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.1.0+12238+63fe3aec | 1:12.22.5-1.module+el8.1.0+12238+63fe3aec |
nodejs-develRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.1.0+12238+63fe3aec | 1:12.22.5-1.module+el8.1.0+12238+63fe3aec |
nodejs-docsRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.1.0+12238+63fe3aec | 1:12.22.5-1.module+el8.1.0+12238+63fe3aec |
nodejs-full-i18nRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 1:12.22.5-1.module+el8.1.0+12238+63fe3aec | 1:12.22.5-1.module+el8.1.0+12238+63fe3aec |
nodejs-nodemonRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 | 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 |
nodejs-packagingRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 0:17-3.module+el8.1.0+3369+37ae6a45 | 0:17-3.module+el8.1.0+3369+37ae6a45 |
npmRed Hat:rhel_eus:8.1::appstream From an advisory covering 11 CVEs |
before 1:6.14.14-1.12.22.5.1.module+el8.1.0+12238+63fe3aec | 1:6.14.14-1.12.22.5.1.module+el8.1.0+12238+63fe3aec |
nodejsRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:14.17.5-1.module+el8.4.0+12247+e2879e58 | 1:14.17.5-1.module+el8.4.0+12247+e2879e58 |
nodejs-debuginfoRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:14.17.5-1.module+el8.4.0+12247+e2879e58 | 1:14.17.5-1.module+el8.4.0+12247+e2879e58 |
nodejs-debugsourceRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:14.17.5-1.module+el8.4.0+12247+e2879e58 | 1:14.17.5-1.module+el8.4.0+12247+e2879e58 |
nodejs-develRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:14.17.5-1.module+el8.4.0+12247+e2879e58 | 1:14.17.5-1.module+el8.4.0+12247+e2879e58 |
nodejs-docsRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:14.17.5-1.module+el8.4.0+12247+e2879e58 | 1:14.17.5-1.module+el8.4.0+12247+e2879e58 |
nodejs-full-i18nRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:14.17.5-1.module+el8.4.0+12247+e2879e58 | 1:14.17.5-1.module+el8.4.0+12247+e2879e58 |
nodejs-nodemonRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 0:2.0.3-1.module+el8.3.0+6519+9f98ed83 | 0:2.0.3-1.module+el8.3.0+6519+9f98ed83 |
nodejs-packagingRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 0:23-3.module+el8.3.0+6519+9f98ed83 | 0:23-3.module+el8.3.0+6519+9f98ed83 |
npmRed Hat:enterprise_linux:8::appstream From an advisory covering 8 CVEs |
before 1:6.14.14-1.14.17.5.1.module+el8.4.0+12247+e2879e58 | 1:6.14.14-1.14.17.5.1.module+el8.4.0+12247+e2879e58 |
nodejsRocky Linux:8 From an advisory covering 8 CVEs |
before 1:12.22.5-1.module+el8.4.0+647+e905fa21 | 1:12.22.5-1.module+el8.4.0+647+e905fa21 |
nodejs-nodemonRocky Linux:8 From an advisory covering 8 CVEs |
before 0:2.0.3-1.module+el8.6.0+982+9fdca2d4 | 0:2.0.3-1.module+el8.6.0+982+9fdca2d4 |
nodejs-nodemonRocky Linux:8 From an advisory covering 8 CVEs |
before 0:2.0.3-1.module+el8.3.0+100+234774f7 | 0:2.0.3-1.module+el8.3.0+100+234774f7 |
nodejs-nodemonRocky Linux:8 From an advisory covering 8 CVEs |
before 0:2.0.3-1.module+el8.4.0+638+5344c6f7 | 0:2.0.3-1.module+el8.4.0+638+5344c6f7 |
nodejs-packagingRocky Linux:8 From an advisory covering 8 CVEs |
before 0:17-3.module+el8.3.0+101+f84c7154 | 0:17-3.module+el8.3.0+101+f84c7154 |
nodejsRocky Linux:8 From an advisory covering 8 CVEs |
before 1:14.17.5-1.module+el8.4.0+654+17ff1d38 | 1:14.17.5-1.module+el8.4.0+654+17ff1d38 |
nodejs-packagingRocky Linux:8 From an advisory covering 8 CVEs |
before 0:23-3.module+el8.7.0+1071+4bdda2a8 | 0:23-3.module+el8.7.0+1071+4bdda2a8 |
nodejs-packagingRocky Linux:8 From an advisory covering 8 CVEs |
before 0:23-3.module+el8.3.0+100+234774f7 | 0:23-3.module+el8.3.0+100+234774f7 |
nodejs-packagingRocky Linux:8 From an advisory covering 8 CVEs |
before 0:23-3.module+el8.5.0+733+de4fee6c | 0:23-3.module+el8.5.0+733+de4fee6c |
tarRoot:npm |
before 4.4.13-aikido.1 | 4.4.13-aikido.1 |
@rootio/tarRoot:npm |
before 4.4.13-root.io.1 | 4.4.13-root.io.1 |
nodejs12SUSE:Linux Enterprise Module for Web and Scripting 12 From an advisory covering 5 CVEs |
before 12.22.10-1.42.2 | 12.22.10-1.42.2 |
nodejs8SUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise Server 15-LTSS From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise Server 15 SP1-BCL From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise Server 15 SP1-LTSS From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Linux Enterprise Server for SAP Applications 15 SP1 From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs8SUSE:Enterprise Storage 6 From an advisory covering 5 CVEs |
before 8.17.0-3.54.2 | 8.17.0-3.54.2 |
nodejs14SUSE:Linux Enterprise Module for Web and Scripting 12 From an advisory covering 5 CVEs |
before 14.19.0-6.24.1 | 14.19.0-6.24.1 |
nodejs10SUSE:Linux Enterprise Module for Web and Scripting 12 From an advisory covering 6 CVEs |
before 10.24.1-1.46.1 | 10.24.1-1.46.1 |
nodejs12SUSE:Linux Enterprise Module for Web and Scripting 15 SP3 From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Linux Enterprise Server 15 SP2-BCL From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Linux Enterprise Server 15 SP2-LTSS From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Linux Enterprise Server for SAP Applications 15 SP2 From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Manager Proxy 4.1 From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Manager Retail Branch Server 4.1 From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Manager Server 4.1 From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs12SUSE:Enterprise Storage 7 From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs-commonSUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Linux Enterprise Server 15-LTSS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise Server 15 SP1-BCL From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise Server 15 SP1-LTSS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise Server 15 SP2-BCL From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Linux Enterprise Server 15 SP2-BCL From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Linux Enterprise Server 15 SP2-LTSS From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Linux Enterprise Server 15 SP2-LTSS From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise Server for SAP Applications 15 SP1 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Linux Enterprise Server for SAP Applications 15 SP2 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Linux Enterprise Server for SAP Applications 15 SP2 From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Manager Proxy 4.1 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Manager Proxy 4.1 From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Manager Retail Branch Server 4.1 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Manager Retail Branch Server 4.1 From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Manager Server 4.1 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Manager Server 4.1 From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs-commonSUSE:Enterprise Storage 6 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs-commonSUSE:Enterprise Storage 7 From an advisory covering 5 CVEs |
before 2.0-3.4.1 | 2.0-3.4.1 |
nodejs8SUSE:Enterprise Storage 7 From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs14SUSE:Linux Enterprise Module for Web and Scripting 15 SP3 From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Linux Enterprise Server 15 SP2-BCL From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Linux Enterprise Server 15 SP2-LTSS From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Linux Enterprise Server for SAP Applications 15 SP2 From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Manager Proxy 4.1 From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Manager Retail Branch Server 4.1 From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Manager Server 4.1 From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs14SUSE:Enterprise Storage 7 From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
nodejs10SUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server 15-LTSS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server 15 SP1-BCL From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server 15 SP1-LTSS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server 15 SP2-BCL From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server 15 SP2-LTSS From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server for SAP Applications 15 SP1 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Linux Enterprise Server for SAP Applications 15 SP2 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Manager Proxy 4.1 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Manager Retail Branch Server 4.1 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Manager Server 4.1 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Enterprise Storage 6 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10SUSE:Enterprise Storage 7 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10openSUSE:Leap 15.3 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
nodejs10openSUSE:Leap 15.4 From an advisory covering 9 CVEs |
before 10.24.1-150000.1.44.1 | 10.24.1-150000.1.44.1 |
node-tarUbuntu:Pro:14.04:LTS |
All versions, plus listed versions 0.1.18-10.1.18-1ubuntu0.1~esm1 |
None known |
node-tarUbuntu:Pro:20.04:LTS |
before 4.4.10+ds1-2ubuntu1+esm1, plus listed versions 4.4.10+ds1-24.4.10+ds1-2ubuntu1 |
4.4.10+ds1-2ubuntu1+esm1 |
nodejs12openSUSE:Leap 15.3 From an advisory covering 5 CVEs |
before 12.22.10-4.29.3 | 12.22.10-4.29.3 |
nodejs8openSUSE:Leap 15.3 From an advisory covering 5 CVEs |
before 8.17.0-10.19.2 | 8.17.0-10.19.2 |
nodejs14openSUSE:Leap 15.3 From an advisory covering 5 CVEs |
before 14.19.0-15.27.1 | 14.19.0-15.27.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | ||
| facts | ||
| affected | ||
| aliases, products | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2021-32803 is a high vulnerability (CVSS 8.2) in Isaacs Node-tar, published August 3, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 7.80%, the 94th percentile. Fixed in tar 4.4.15.
References
github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw
github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20
npmjs.com/advisories/1771
npmjs.com/package/tar
oracle.com/security-alerts/cpuoct2021.html
cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
Show 140 moreShow less
nvd.nist.gov/vuln/detail/CVE-2021-32803
github.com/isaacs/node-tar/commit/46fe35083e2676e31c4e0a81639dce6da7aaa356
github.com/isaacs/node-tar/commit/5987d9a41f6bfbf1ddab1098e1fdcf1a5618f571
github.com/isaacs/node-tar/commit/85d3a942b4064e4ff171f91696fced7975167349
github.com/isaacs/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20
github.com/advisories/GHSA-r628-mhmh-qjhw
security.alpinelinux.org/vuln/CVE-2021-32803
access.redhat.com/errata/RHSA-2021:3623
bugzilla.redhat.com/1956818
bugzilla.redhat.com/1988342
bugzilla.redhat.com/1988394
bugzilla.redhat.com/1990409
bugzilla.redhat.com/1990415
bugzilla.redhat.com/1993019
bugzilla.redhat.com/1993029
bugzilla.redhat.com/1993039
bugzilla.redhat.com/1993927
errata.almalinux.org/8/ALSA-2021-3623.html
vulners.com/cve/CVE-2021-22930
vulners.com/cve/CVE-2021-22931
vulners.com/cve/CVE-2021-22939
vulners.com/cve/CVE-2021-22940
vulners.com/cve/CVE-2021-23343
vulners.com/cve/CVE-2021-32803
vulners.com/cve/CVE-2021-32804
vulners.com/cve/CVE-2021-3672
access.redhat.com/errata/RHSA-2021:3666
bugzilla.redhat.com/1993924
errata.almalinux.org/8/ALSA-2021-3666.html
docs.bell-sw.com/security/cves/CVE-2021-32803
security-tracker.debian.org/tracker/CVE-2021-32803
github.com/isaacs/node-tar
advisories.mageia.org/MGASA-2022-0103.html
bugs.mageia.org/show_bug.cgi?id=29656
debian.org/security/2021/dsa-5008
access.redhat.com/errata/RHSA-2021:3280
access.redhat.com/security/updates/classification
bugzilla.redhat.com/show_bug.cgi?id=1907444
bugzilla.redhat.com/show_bug.cgi?id=1945459
bugzilla.redhat.com/show_bug.cgi?id=1956818
bugzilla.redhat.com/show_bug.cgi?id=1988342
bugzilla.redhat.com/show_bug.cgi?id=1988394
bugzilla.redhat.com/show_bug.cgi?id=1990409
bugzilla.redhat.com/show_bug.cgi?id=1990415
bugzilla.redhat.com/show_bug.cgi?id=1993019
bugzilla.redhat.com/show_bug.cgi?id=1993029
bugzilla.redhat.com/show_bug.cgi?id=1993039
security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_3280.json
access.redhat.com/security/cve/CVE-2020-7788
cve.org/CVERecord?id=CVE-2020-7788
nvd.nist.gov/vuln/detail/CVE-2020-7788
access.redhat.com/security/cve/CVE-2020-28469
cve.org/CVERecord?id=CVE-2020-28469
nvd.nist.gov/vuln/detail/CVE-2020-28469
snyk.io/vuln/SNYK-JS-GLOBPARENT-1016905
access.redhat.com/security/cve/CVE-2021-3672
cve.org/CVERecord?id=CVE-2021-3672
nvd.nist.gov/vuln/detail/CVE-2021-3672
c-ares.haxx.se/adv_20210810.html
access.redhat.com/security/cve/CVE-2021-22930
cve.org/CVERecord?id=CVE-2021-22930
nvd.nist.gov/vuln/detail/CVE-2021-22930
access.redhat.com/security/cve/CVE-2021-22931
cve.org/CVERecord?id=CVE-2021-22931
nvd.nist.gov/vuln/detail/CVE-2021-22931
nodejs.org/en/blog/vulnerability/aug-2021-security-releases
access.redhat.com/security/cve/CVE-2021-22939
cve.org/CVERecord?id=CVE-2021-22939
nvd.nist.gov/vuln/detail/CVE-2021-22939
access.redhat.com/security/cve/CVE-2021-22940
cve.org/CVERecord?id=CVE-2021-22940
nvd.nist.gov/vuln/detail/CVE-2021-22940
access.redhat.com/security/cve/CVE-2021-23343
cve.org/CVERecord?id=CVE-2021-23343
nvd.nist.gov/vuln/detail/CVE-2021-23343
snyk.io/vuln/SNYK-JS-PATHPARSE-1077067
access.redhat.com/security/cve/CVE-2021-32803
cve.org/CVERecord?id=CVE-2021-32803
access.redhat.com/security/cve/CVE-2021-32804
cve.org/CVERecord?id=CVE-2021-32804
nvd.nist.gov/vuln/detail/CVE-2021-32804
github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9
access.redhat.com/errata/RHSA-2021:3281
security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_3281.json
bugzilla.redhat.com/show_bug.cgi?id=1993927
security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_3623.json
access.redhat.com/errata/RHSA-2021:3638
bugzilla.redhat.com/show_bug.cgi?id=1941471
bugzilla.redhat.com/show_bug.cgi?id=1943208
bugzilla.redhat.com/show_bug.cgi?id=1979338
bugzilla.redhat.com/show_bug.cgi?id=1993928
security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_3638.json
access.redhat.com/security/cve/CVE-2021-22918
cve.org/CVERecord?id=CVE-2021-22918
nvd.nist.gov/vuln/detail/CVE-2021-22918
nodejs.org/en/blog/vulnerability/july-2021-security-releases
access.redhat.com/security/cve/CVE-2021-23362
cve.org/CVERecord?id=CVE-2021-23362
nvd.nist.gov/vuln/detail/CVE-2021-23362
access.redhat.com/security/cve/CVE-2021-27290
cve.org/CVERecord?id=CVE-2021-27290
nvd.nist.gov/vuln/detail/CVE-2021-27290
access.redhat.com/errata/RHSA-2021:3639
bugzilla.redhat.com/show_bug.cgi?id=1993929
security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_3639.json
bugzilla.redhat.com/show_bug.cgi?id=1993924
security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_3666.json
errata.rockylinux.org/RLSA-2021:3623
errata.rockylinux.org/RLSA-2021:3666
suse.com/support/update/announcement/2022/suse-su-20220531-1
bugzilla.suse.com/1191962
bugzilla.suse.com/1191963
bugzilla.suse.com/1192153
bugzilla.suse.com/1192154
bugzilla.suse.com/1192696
suse.com/security/cve/CVE-2021-23343
suse.com/security/cve/CVE-2021-32803
suse.com/security/cve/CVE-2021-32804
suse.com/security/cve/CVE-2021-3807
suse.com/security/cve/CVE-2021-3918
suse.com/support/update/announcement/2022/suse-su-20220563-1
suse.com/support/update/announcement/2022/suse-su-20220569-1
suse.com/support/update/announcement/2022/suse-su-20220570-1
bugzilla.suse.com/1194514
suse.com/security/cve/CVE-2022-21824
suse.com/support/update/announcement/2022/suse-su-20220657-1
suse.com/support/update/announcement/2022/suse-su-20220704-1
suse.com/support/update/announcement/2022/suse-su-20220715-1
suse.com/support/update/announcement/2022/suse-su-20221717-1
bugzilla.suse.com/1194819
bugzilla.suse.com/1197283
bugzilla.suse.com/1198247
suse.com/security/cve/CVE-2021-44906
suse.com/security/cve/CVE-2021-44907
suse.com/security/cve/CVE-2022-0235
ubuntu.com/security/CVE-2021-32803
ubuntu.com/security/notices/USN-5283-1
lists.opensuse.org/archives/list/[email protected]/thread/NCH4EEBMT6XZIRNVGTNBOCQCY4JVZ4IN
lists.opensuse.org/archives/list/[email protected]/thread/4BTHU2F626CTZYCXOBT5S7GWU3QXNTMZ
lists.opensuse.org/archives/list/[email protected]/thread/VAM6LOV2R24IH5PPUWLXB64PALLMBOTU