BillionMail through 4.9 Forgeable JWTs via Default Signing Key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| aaPanel | BillionMail | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aapanel | Billionmail |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.332% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aapanel
Aapanel billionmail |
|
| Vendors & Products |
Aapanel
Aapanel billionmail |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | BillionMail through 4.9 contains a hard-coded cryptographic key vulnerability that allows unauthenticated attackers to forge unsubscribe and subscribe-confirm JWTs by computing the key from shipped configuration constants. Attackers can submit forged tokens to /api/unsubscribe, /api/unsubscribe_new, or /api/subscribe/confirm to deactivate any contact or force confirmed subscriptions. | |
| Title | BillionMail through 4.9 Forgeable JWTs via Default Signing Key | |
| Weaknesses | CWE-1394 | |
| References |
|
|
| Metrics |
cvssV3_1
|