Link Following Affecting nodejs-full-i18n package, versions <1:12.22.5-1.module+el8.4.0+20308+065a70e3
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ORACLE8-NODEJSFULLI18N-2589541
- published 10 Apr 2022
- disclosed 3 Aug 2021
Introduced: 3 Aug 2021
CVE-2021-32803 Open this link in a new tabHow to fix?
Upgrade Oracle:8 nodejs-full-i18n to version 1:12.22.5-1.module+el8.4.0+20308+065a70e3 or higher.
This issue was patched in ELSA-2021-3623.
NVD Description
Note: Versions mentioned in the description apply only to the upstream nodejs-full-i18n package and not the nodejs-full-i18n package as distributed by Oracle.
See How to fix? for Oracle:8 relevant fixed versions and status.
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.
References
- https://linux.oracle.com/cve/CVE-2021-32803.html
- https://linux.oracle.com/errata/ELSA-2021-3623.html
- https://linux.oracle.com/errata/ELSA-2021-3666.html
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20
- https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw
- https://www.npmjs.com/advisories/1771
- https://www.npmjs.com/package/tar
- https://www.oracle.com/security-alerts/cpuoct2021.html