CVE-2025-6547

Improper Input Validation (CWE-20)

Published: Jun 23, 2025 / Updated: 2d ago

010
High Severity
(Estimated)
EPSS 0.09%
CVE info copied to clipboard

Summary

A vulnerability related to static hash generation in Node.js/io.js versions prior to 3.0.0, where static hashes are outputted and used as keys or passwords, which can completely undermine security. The issue involves improper input validation that allows generation of predictable or insecure cryptographic keys.

Impact

An attacker could potentially: - Exploit predictable cryptographic keys - Compromise system security by using static, weak hash generation - Gain unauthorized access to systems using vulnerable Node.js versions - Potentially decrypt or manipulate cryptographically protected data

Exploitation

There is no evidence that a public proof-of-concept exists. There is no evidence of proof of exploitation at the moment.

Patch

Patches are available through GitHub Advisory and Red Hat

Mitigation

Immediate recommended actions: - Upgrade Node.js/io.js to version 3.0.0 or later - Audit all systems using Node.js versions < 3.0.0 - Review and regenerate any cryptographic keys generated during vulnerable period - Verify no residual static hash usage in critical systems

Timeline

Vendor Advisory

GitHub Advisories released a security advisory.

Jun 23, 2025 at 7:01 PM
CVE Assignment

NVD published the first details for CVE-2025-6547

Jun 23, 2025 at 7:15 PM
CVSS

A CVSS base score of 9.1 has been assigned.

Jun 23, 2025 at 7:20 PM / nvd
First Article

Feedly found the first article mentioning CVE-2025-6547. See article

Jun 23, 2025 at 7:21 PM / National Vulnerability Database
CVSS Estimate

Feedly estimated the CVSS score as HIGH

Jun 23, 2025 at 7:21 PM
Vendor Advisory

RedHat CVE advisory released a security advisory (CVE-2025-6547).

Jun 23, 2025 at 11:25 PM
CVSS

A CVSS base score of 8.1 has been assigned.

Jun 23, 2025 at 11:25 PM / redhat-cve-advisories
EPSS

FIRST assigned an EPSS Score of 0.04% (Percentile: 12.2%)

Jun 24, 2025 at 2:55 PM
EPSS

FIRST assigned an EPSS Score of 0.09% (Percentile: 25.7%)

Jun 25, 2025 at 10:02 PM
Static CVE Timeline Graph

Affected Systems

Apache
+null more

Patches

Github Advisory
+null more

Links to Mitre Att&cks

T1562.003: Impair Command History Logging
+null more

Attack Patterns

CAPEC-10: Buffer Overflow via Environment Variables
+null more

Vendor Advisory

[GHSA-v62p-rq8g-8h59] pbkdf2 silently disregards Uint8Array input, returning static keys

GitHub Security Advisory: GHSA-v62p-rq8g-8h59 Release Date: 2025-06-23 Update Date: 2025-06-23 Severity: Critical CVE-2025-6547 Package Information Package: pbkdf2 Affected Versions: Patched Versions: 3.1.3 Description Static hashes being outputted and used as keys/passwords can completely undermine security That said, no one should be using those Node.js versions anywhere now, so I would recommend to just drop them This lib should not pretend to work on those versions while outputting static data though Just updating to a fixed version is not enough: if anyone was using pbkdf2 lib (do not confuse with Node.js crypto.pbkdf2) or anything depending on it with Node.js/io.js Details The error is in toBuffer method This vulnerability somehow even made it to tests: browserify/pbkdf2@eb9f97a There, resultsOld (where mismatch results) are just invalid output generated from empty password/salt instead of the supplied one Poc On Node.js/io.js require('pbkdf2').pbkdf2Sync(new Uint8Array([1,2,3]), new Uint8Array([1,3,4]), 1024, 32, 'sha256')

News

Fedora EPEL 8 update for yarnpkg

The vulnerability allows a remote attacker to perform a spoofing attack. Risk Medium Patch available YES Number of vulnerabilities 2 CVE-ID CVE-2025-6547

CVE-2025-6547

Critical Severity Description Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation.This issue affects pbkdf2: Read more at https://www.tenable.com/cve/CVE-2025-6547

CVE-2025-6547

CVE Id: CVE-2025-6547 Release Date: 2025-06-23 Update Date: 2025-06-23 Impact Important CVSS Base Score: 8.1 Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Description No description is available for this CVE. Mitigation Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

[GHSA-v62p-rq8g-8h59] pbkdf2 silently disregards Uint8Array input, returning static keys

GitHub Security Advisory: GHSA-v62p-rq8g-8h59 Release Date: 2025-06-23 Update Date: 2025-06-23 Severity: Critical CVE-2025-6547 Package Information Package: pbkdf2 Affected Versions: Patched Versions: 3.1.3 Description Static hashes being outputted and used as keys/passwords can completely undermine security That said, no one should be using those Node.js versions anywhere now, so I would recommend to just drop them This lib should not pretend to work on those versions while outputting static data though Just updating to a fixed version is not enough: if anyone was using pbkdf2 lib (do not confuse with Node.js crypto.pbkdf2) or anything depending on it with Node.js/io.js Details The error is in toBuffer method This vulnerability somehow even made it to tests: browserify/pbkdf2@eb9f97a There, resultsOld (where mismatch results) are just invalid output generated from empty password/salt instead of the supplied one Poc On Node.js/io.js require('pbkdf2').pbkdf2Sync(new Uint8Array([1,2,3]), new Uint8Array([1,3,4]), 1024, 32, 'sha256')

NA - CVE-2025-6547 - Improper Input Validation vulnerability in...

Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing by Improper Validation.This issue affects pbkdf2:
See 5 more articles and social media posts

CVSS V3.1

Unknown

Categories

Be the first to know about critical vulnerabilities

Collect, analyze, and share vulnerability reports faster using AI

OSZAR »