Kubero 3.0.0 through 3.1.1 Authentication Bypass via Hardcoded JWT Secret
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| kubero-dev | kubero | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Kubero-dev | Kubero |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.683% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Kubero-dev
Kubero-dev kubero |
|
| Vendors & Products |
Kubero-dev
Kubero-dev kubero |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kubero 3.0.0 through 3.1.1 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to forge administrative JWTs by using a hardcoded fallback signing secret when JWT_SECRET is unset. Attackers can sign tokens with arbitrary role, userGroups and permissions claims, which JwtStrategy.validate() trusts without a database lookup, to take control of pipelines, applications, users and API tokens. | |
| Title | Kubero 3.0.0 through 3.1.1 Authentication Bypass via Hardcoded JWT Secret | |
| Weaknesses | CWE-321 | |
| References |
|
|
| Metrics |
cvssV3_1
|