Peppermint through 0.5.5 Use of Hard-coded JWT Signing Secret in docker-compose.yml
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Peppermint-Lab | peppermint | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Peppermint | Peppermint |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.641% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Peppermint through 0.5.5 contains a hardcoded JWT signing secret in docker-compose.yml that allows unauthenticated attackers to forge session tokens for any account. Attackers can use the published secret to mint valid tokens for arbitrary user IDs and access protected endpoints without credentials. | |
| Title | Peppermint through 0.5.5 Use of Hard-coded JWT Signing Secret in docker-compose.yml | |
| First Time appeared |
Peppermint
Peppermint peppermint |
|
| Weaknesses | CWE-798 | |
| CPEs | cpe:2.3:a:peppermint:peppermint:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Peppermint
Peppermint peppermint |
|
| References |
|
|
| Metrics |
cvssV3_1
|