Skip to content
Fallow home
All docs pages

Docs home

Unsafe Buffer allocation sink

What an unsafe-buffer-alloc finding of fallow security means, why it matters and how to fix it.

What it reports

Catalogue security candidate for CWE-1188.

Security explains how fallow finds it.

Why it matters

The buffer holds old memory of the process until the code overwrites it. If the code sends the buffer before it fills it, earlier data such as secrets can leak.

Example

Buffer.allocUnsafe(Number(req.query.size));

Fix

Review the candidate trace before acting. Confirm attacker control, missing sanitization, and reachable runtime context, then fix with the category-appropriate safer API or add a reviewed suppression.

Facts

FactValue
Issue typeunsafe-buffer-alloc
Rule id in SARIF outputsecurity/unsafe-buffer-alloc
Commandfallow security
Default severityoff
Suppression comment// fallow-ignore-next-line security-sink
Fixable with fallow fixNo
Opt-inYes

Note. Tainted-sink catalogue category; the security-sink suppression token covers every category.