Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2cjv-6wg9-f4f3 | Strapi Password Hashing Missing Maximum Password Length Validation |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 20 Oct 2025 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Strapi
Strapi strapi |
|
| Vendors & Products |
Strapi
Strapi strapi |
Thu, 16 Oct 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 16 Oct 2025 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Strapi is an open source headless CMS. The @strapi/core package before version 5.10.3 does not enforce a maximum password length when using bcryptjs for password hashing. Bcryptjs ignores any bytes beyond 72, so passwords longer than 72 bytes are silently truncated. A user can create an account with a password exceeding 72 bytes and later authenticate with only the first 72 bytes. This reduces the effective entropy of overlong passwords and may mislead users who believe characters beyond 72 bytes are required, creating a low likelihood of unintended authentication if an attacker can obtain or guess the truncated portion. Long over‑length inputs can also impose unnecessary processing overhead. The issue is fixed in version 5.10.3. No known workarounds exist. | |
| Title | Missing Maximum Password Length Validation in Strapi Password Hashing | |
| Weaknesses | CWE-261 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-10-16T18:12:49.837Z
Reserved: 2025-02-06T17:13:33.123Z
Link: CVE-2025-25298
Updated: 2025-10-16T18:12:45.876Z
Status : Awaiting Analysis
Published: 2025-10-16T17:15:33.353
Modified: 2025-10-21T19:31:50.020
Link: CVE-2025-25298
No data.
OpenCVE Enrichment
Updated: 2025-10-20T13:25:15Z
Github GHSA