Security context

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

brix/crypto-js

              develop @ ac34a5a
            

Fixes

CVEs

CRITICAL

Peak severity

Highlights

Insecure Randomness: 2 prior fixes. Scrutinize any change in this area.

src/core.js: most-fixed (3 issues). Treat as high-risk during review.

1 high-severity fix in this history; regressions here are high-impact.

Recurring patterns

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

Weak Cryptographic Algorithm: The PBKDF2 implementation historically defaulted to a single iteration and used SHA-1 as its pseudorandom function. This critical weakness allowed attackers to perform rapid offline brute-force attacks against derived keys when default configurations were utilized.

Insecure Randomness: The library historically generated entropy for WordArrays using Math.random() or structured string concatenations rather than secure native APIs. This allowed attackers to predict generated keys and initial vectors, fully compromising transitively secured payloads.

Cryptographic Issues: Even when attempting to consume native, cryptographically secure APIs, a post-processing bitwise OR operation (forcing the least significant bit to 1) was applied to the secure values. This implementation mistake systematically stripped entropy from the generated random numbers.