Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

ranisalt/node-argon2
master @ 60e11ef
3
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Buffer Overflow: 1 prior fix. Scrutinize any change in this area.
src/argon2_node.cpp: most-fixed (2 issues). Treat as high-risk during review.
2 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Buffer Overflow: Inadequate allocation sizing when interfacing with the underlying `argon2_hash` function can cause a heap buffer overflow. Correcting this requires dynamic allocation based on the calculated length of the encoded Argon2 hash.
Memory Corruption: Using standard C-string duplication utilities like `strdup` on binary buffers containing null bytes leads to premature truncation and potentially unsafe memory manipulation. Handling hash data safely requires using Node-native raw data copy utilities like `Nan::CopyBuffer`.
Security Misconfiguration: Over-privileged GitHub Actions workflows create a posture risk where compromised dependencies or pull requests could abuse write permissions on the repository. Access must be limited using explicit read-only scopes.