vlife through 2.0.1 Authentication Bypass via Hardcoded JWT Secret in TokenUtil
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| wwwlike | vlife | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wwwlike | Vlife |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.995% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wwwlike
Wwwlike vlife |
|
| Vendors & Products |
Wwwlike
Wwwlike vlife |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vlife through 2.0.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge JWTs using the hardcoded HS256 signing key in TokenUtil. Attackers can sign a token with superUser=true and arbitrary groupIds claims to gain super administrator access to any URL on vlife instances. | |
| Title | vlife through 2.0.1 Authentication Bypass via Hardcoded JWT Secret in TokenUtil | |
| Weaknesses | CWE-321 | |
| References |
|
|
| Metrics |
cvssV3_1
|