Kubero through 3.1.1 Unauthenticated Notifications API Access
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.632% probability within 30 days)
| 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 |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kubero through 3.1.1 fails to apply authentication guards to the notifications API endpoints, allowing unauthenticated attackers to read webhook secrets and service URLs. Attackers can retrieve stored credentials and register malicious webhooks to intercept pipeline events or suppress alerting by deleting existing configurations. | |
| Title | Kubero through 3.1.1 Unauthenticated Notifications API Access | |
| Weaknesses | CWE-306 | |
| References |
|
|
| Metrics |
cvssV3_1
|