Advisory

DEBIAN-CVE-2021-37712

Also known as: CVE-2021-37712

Summary

The record has no summary.

Details

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

Severity

High Basis: CVSS v3 score 8.6, vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Dates

Published
2021-08-31 17:15 UTC
Modified
2026-10-23 18:03 UTC

Affected packages and fixes

node-tar

Debian packages (deb) · Debian 12

Affected

  • introduced 0, fixed 6.1.11+~cs11.3.10-1 (ecosystem)

Fixed versions

6.1.11+~cs11.3.10-1

Fix

  • Fixed version 6.1.11+~cs11.3.10-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

node-tar

Debian packages (deb) · Debian 13

Affected

  • introduced 0, fixed 6.1.11+~cs11.3.10-1 (ecosystem)

Fixed versions

6.1.11+~cs11.3.10-1

Fix

  • Fixed version 6.1.11+~cs11.3.10-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

node-tar

Debian packages (deb) · Debian 14

Affected

  • introduced 0, fixed 6.1.11+~cs11.3.10-1 (ecosystem)

Fixed versions

6.1.11+~cs11.3.10-1

Fix

  • Fixed version 6.1.11+~cs11.3.10-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Debian Security Tracker (converted by OSV.dev)

Debian Security Tracker, converted to OSV by OSV.dev.

Sources & licences