https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 23:04:21 +0000 https://vulnerability.circl.lu/vuln/cve-2025-6545 <p><strong>Affected:</strong> pbkdf2</p> <p>Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/to-buffer.Js.</p> <p>This issue affects pbkdf2: from 3.0.10 through 3.1.2.</p> <p><strong>Affected:</strong> pbkdf2</p> <p>Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation. This vulnerability is associated with program files lib/to-buffer.Js.</p> <p>This issue affects pbkdf2: from 3.0.10 through 3.1.2.</p> https://vulnerability.circl.lu/vuln/cve-2025-6545 https://vulnerability.circl.lu/vuln/ghsa-h7cp-r72f-jxh6 <p><strong>Affected:</strong> npm: pbkdf2</p> <p>### Summary</p> <p>This affects both: 1. Unsupported algos (e.g. `sha3-256` / `sha3-512` / `sha512-256`) 2. Supported but non-normalized algos (e.g. `Sha256` / `Sha512` / `SHA1` / `sha-1` / `sha-256` / `sha-512`)</p> <p>All of those work correctly in Node.js, but this polyfill silently returns highly predictable ouput</p> <p>Under Node.js (only with `pbkdf2/browser` import, unlikely) / Bun (`pbkdf2` top-level import is affected), the memory is not zero-filled but is uninitialized, as `Buffer.allocUnsafe` is used</p> <p>Under browsers, it just returns zero-filled buffers (Which is also critical, those are completely unacceptable as kdf output and ruin security)</p> <p>### Were you affected?</p> <p>The full list of arguments that were **not** affected were literal: * `&#39;md5&#39;` * `&#39;sha1&#39;` * `&#39;sha224&#39;` * `&#39;sha256&#39;` * `&#39;sha384&#39;` * `&#39;sha512&#39;` * `&#39;rmd160&#39;` * `&#39;ripemd160&#39;`</p> <p>Any other arguments, e.g. representation variations of the above ones like `&#39;SHA-1&#39;`/`&#39;sha-256&#39;`/`&#39;SHA512&#39;` or different algos like `&#39;sha3-512&#39;`/`&#39;blake2b512&#39;`, while supported on Node.js `crypto` module, returned predictable output on `pbkdf2` (or `crypto` browser/bundlers polyfill)</p> <p>---</p> <p>Beware of packages re-exporting this under a different signature, like (abstract): ```js const crypto = require(&#39;crypto&#39;) module.exports.deriveKey = (algo, pass, salt) =&gt; crypto.pbkdf2Sync(pass, salt, 2048, 64, algo) ```</p> <p>In this case, the resulting `deriveKey` method is also affected (to the same extent / conditions as listed here).</p> <p>### Environments</p> <p>T…</p> <p><strong>Affected:</strong> npm: pbkdf2</p> <p>### Summary</p> <p>This affects both: 1. Unsupported algos (e.g. `sha3-256` / `sha3-512` / `sha512-256`) 2. Supported but non-normalized algos (e.g. `Sha256` / `Sha512` / `SHA1` / `sha-1` / `sha-256` / `sha-512`)</p> <p>All of those work correctly in Node.js, but this polyfill silently returns highly predictable ouput</p> <p>Under Node.js (only with `pbkdf2/browser` import, unlikely) / Bun (`pbkdf2` top-level import is affected), the memory is not zero-filled but is uninitialized, as `Buffer.allocUnsafe` is used</p> <p>Under browsers, it just returns zero-filled buffers (Which is also critical, those are completely unacceptable as kdf output and ruin security)</p> <p>### Were you affected?</p> <p>The full list of arguments that were **not** affected were literal: * `&#39;md5&#39;` * `&#39;sha1&#39;` * `&#39;sha224&#39;` * `&#39;sha256&#39;` * `&#39;sha384&#39;` * `&#39;sha512&#39;` * `&#39;rmd160&#39;` * `&#39;ripemd160&#39;`</p> <p>Any other arguments, e.g. representation variations of the above ones like `&#39;SHA-1&#39;`/`&#39;sha-256&#39;`/`&#39;SHA512&#39;` or different algos like `&#39;sha3-512&#39;`/`&#39;blake2b512&#39;`, while supported on Node.js `crypto` module, returned predictable output on `pbkdf2` (or `crypto` browser/bundlers polyfill)</p> <p>---</p> <p>Beware of packages re-exporting this under a different signature, like (abstract): ```js const crypto = require(&#39;crypto&#39;) module.exports.deriveKey = (algo, pass, salt) =&gt; crypto.pbkdf2Sync(pass, salt, 2048, 64, algo) ```</p> <p>In this case, the resulting `deriveKey` method is also affected (to the same extent / conditions as listed here).</p> <p>### Environments</p> <p>T…</p> https://vulnerability.circl.lu/vuln/ghsa-h7cp-r72f-jxh6