Predictable derived keys via unvalidated digest names
Published Jun 23, 2025 · Updated Jun 23, 2025
Improper input validation in Browserify PBKDF2 3.0.10 through 3.1.2 allows remote attackers to obtain predictable keys via digest names. lib/sync.js indexes a literal digest-size table without normalizing or rejecting the digest name, so its HMAC path leaves allocated key bytes unwritten. Exposure requires a nonlisted algorithm spelling in the browser implementation or browser import; browsers return zero-filled keys, while Node.js and Bun can expose uninitialized memory.
Summary
What happened
Improper input validation in Browserify PBKDF2 3.0.10 through 3.1.2 allows remote attackers to obtain predictable keys via digest names. lib/sync.js indexes a literal digest-size table without normalizing or rejecting the digest name, so its HMAC path leaves allocated key bytes unwritten. Exposure requires a nonlisted algorithm spelling in the browser implementation or browser import; browsers return zero-filled keys, while Node.js and Bun can expose uninitialized memory.
The record
- CVE
- CVE-2025-6545
- Published
- Jun 23, 2025
- Updated
- Jun 23, 2025
- Vendor
- Browserify
- Product
- PBKDF2
- Classifications
- CWE-20, CAPEC-475, T1600.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2025CVE publishedPublication date reported by the CVE source.
- Jun 23, 2025Record 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=3.0.10 <=3.1.2
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
- Upstream predictable-key proof of conceptproof of concept · demonstrated
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