GHSA-8x88-c5mf-7j5w — node-tar: Negative tar entry size causes infinite loop in archive replace

Affected: npm: tar

### Summary

A checksum-valid tar archive with a negative base-256 encoded entry size can make `tar.replace()` loop forever while scanning the existing archive. Applications that update attacker-controlled tar archives can have a worker process pinned indefinitely, causing denial of service.

### Details

The public `tar.replace()` API scans the existing archive before appending replacement entries. During this scan, it parses each tar header and advances the archive position by the parsed entry size rounded to a 512-byte block boundary.

Tar supports base-256 encoded numeric fields. A crafted header can encode the entry size as `-512` while still carrying a valid checksum. The replace scan accepts that parsed negative size and uses it in the position-advance calculation.

For a size of `-512`, the computed body skip is `-512`. The scan then adds the normal 512-byte header step, resulting in no net progress. The scanner repeatedly parses the same header forever and never reaches the append step.

This is reachable through the supported package API when the existing archive file is attacker controlled. It does not rely on extraction, dependency behavior, or an uncaught exception.

### PoC

Save as `poc.mjs` in a project with the vulnerable package installed and run:

```bash node poc.mjs ```

```js import fs from 'node:fs' import os from 'node:os' import path from 'node:path' import { spawnSync } from 'node:child_process'

const oct = (b, n, off, len) => b.write(n.toString(…

Most recent entries from all

GHSA-8x88-c5mf-7j5w — node-tar: Negative tar entry size causes infinite loop in archive replace