Crawlab through 0.6.3 Authentication Bypass via Hard-coded 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 | ||||||
|---|---|---|---|---|---|---|---|---|---|
| crawlab-team | crawlab | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Crawlab-team | Crawlab |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.765% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Crawlab-team
Crawlab-team crawlab |
|
| Vendors & Products |
Crawlab-team
Crawlab-team crawlab |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Crawlab through 0.6.3 uses a hard-coded HMAC-SHA256 secret for JWT token signing that cannot be overridden via configuration or environment variables. Unauthenticated attackers can forge valid administrator tokens to access administrative APIs and execute code on worker nodes. | |
| Title | Crawlab through 0.6.3 Authentication Bypass via Hard-coded JWT Secret | |
| Weaknesses | CWE-321 | |
| References |
|
|
| Metrics |
cvssV3_1
|