opengoofy/hippo4j · Security
hippo4j Includes Hard Coded Secret Key in JWT Creation
- GHSA ID
- GHSA-48cg-9c55-j2q7
- CVE ID
- CVE-2025-51606
- Severity
- high
- Published
- Updated
- CVSS
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS v3
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Description
hippo4j 1.0.0 to 1.5.0, uses a hard-coded secret key in its JWT (JSON Web Token) creation. This allows attackers with access to the source code or compiled binary to forge valid access tokens and impersonate any user, including privileged ones such as "admin". The vulnerability poses a critical security risk in systems where authentication and authorization rely on the integrity of JWTs.
CWEs
- CWE-798 · Use of Hard-coded Credentials
References
- https://nvd.nist.gov/vuln/detail/CVE-2025-51606 ↗
- https://github.com/ShenxiuSec/cve-proofs/blob/main/POC-20250610-01.md ↗
- https://github.com/opengoofy/hippo4j/blob/7d78be3cab526501ad876495862f4cec108da2af/threadpool/server/auth/src/main/java/cn/hippo4j/auth/security/JwtTokenManager.java#L51 ↗
- https://github.com/advisories/GHSA-48cg-9c55-j2q7 ↗