Kubero through 3.1.1 Unauthenticated Notifications API Access
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.3epss 0.5%
exploitation probability
0.5%top 60% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
kubero-dev · kuberoReferences
https://github.com/kubero-dev/kuberohttps://github.com/kubero-dev/kubero/blob/v3.1.1/server/src/main.tshttps://github.com/kubero-dev/kubero/blob/v3.1.1/server/src/notifications/notifications.controller.ts#L23-L33https://github.com/kubero-dev/kubero/issues/753https://www.vulncheck.com/advisories/kubero-through-3.1.1-unauthenticated-notifications-api-access