Your submission was sent successfully! Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2021-32803

Published: 3 August 2021

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.

Priority

Medium

Cvss 3 Severity Score

8.1

Score breakdown

Status

Package Release Status
node-tar
Launchpad, Ubuntu, Debian
bionic Not vulnerable
(code not present)
focal
Released (4.4.10+ds1-2ubuntu1+esm1)
Available with Ubuntu Pro
hirsute Ignored
(end of life)
impish Not vulnerable
(6.1.2)
jammy Not vulnerable
(6.1.2)
kinetic Not vulnerable
(6.1.2)
lunar Not vulnerable
(6.1.2)
mantic Not vulnerable
(6.1.2)
trusty Needs triage

upstream
Released (3.2.3, 4.4.15, 5.0.7, 6.1.2)
xenial Not vulnerable
(6.1.2)

Severity score breakdown

Parameter Value
Base score 8.1
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Scope Unchanged
Confidentiality None
Integrity impact High
Availability impact High
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H