Secret recovery via one-iteration PBKDF2 default
Published Oct 25, 2023 · Updated Jun 23, 2026
Weak PBKDF2 defaults in Brix crypto-js before 4.2.0 allow attackers to recover protected secrets through offline brute force. The PBKDF2 configuration in src/pbkdf2.js selects SHA-1 and one iteration when callers omit options, removing the intended computational cost. Exploitation requires access to a derived value and affects only applications that rely on the defaults, but recovered keys or passwords can expose or undermine protected data.
Summary
What happened
Weak PBKDF2 defaults in Brix crypto-js before 4.2.0 allow attackers to recover protected secrets through offline brute force. The PBKDF2 configuration in src/pbkdf2.js selects SHA-1 and one iteration when callers omit options, removing the intended computational cost. Exploitation requires access to a derived value and affects only applications that rely on the defaults, but recovered keys or passwords can expose or undermine protected data.
The record
- CVE
- CVE-2023-46233
- Published
- Oct 25, 2023
- Updated
- Jun 23, 2026
- Vendor
- Brix
- Product
- crypto-js
- Classifications
- CWE-328, CWE-916, T1110.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo