Home
» GitHub Advisories
» GHSA-48cg-9c55-j2q7
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.
Basic information
Type
reviewed
Severity
high Advisory on GitHub
Open advisory ↗ Repository advisory
—
Source code
Browse source ↗ Published (advisory)
2025-08-21 21:32:08 UTC
Updated
2025-08-22 20:30:16 UTC
GitHub reviewed
2025-08-22 20:30:13 UTC
NVD published
2025-08-21
EPSS Score
Score
Percentile
0.07%
21.09%
CVSS Scores
Base score
Version
Severity
Vector
8.8
3.1
—
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
CWEs
CWE id
Name
CWE-798
Use of Hard-coded Credentials
Affected packages (1)
Vulnerable version ranges and first patched releases as published by GitHub.
Ecosystem
Package
Vulnerable range
First patched
Vulnerable functions
maven
cn.hippo4j:hippo4j-core >= 1.0.0, <= 1.5.0
—
—
cvelogic
Threat Intelligence