Skip to content

Alertmanager UI is vulnerable to stored XSS via the /api/v1/alerts endpoint

Moderate severity GitHub Reviewed Published Aug 23, 2023 in prometheus/alertmanager • Updated Nov 12, 2023

Package

gomod github.com/prometheus/alertmanager (Go)

Affected versions

<= 0.25.0

Patched versions

0.25.1

Description

Impact

An attacker with the permission to perform POST requests on the /api/v1/alerts endpoint could be able to execute arbitrary JavaScript code on the users of Prometheus Alertmanager.

Patches

Users can upgrade to Alertmanager v0.2.51.

Workarounds

Users can setup a reverse proxy in front of the Alertmanager web server to forbid access to the /api/v1/alerts endpoint.

References

N/A

References

@simonpasquier simonpasquier published to prometheus/alertmanager Aug 23, 2023
Published to the GitHub Advisory Database Aug 23, 2023
Reviewed Aug 23, 2023
Published by the National Vulnerability Database Aug 25, 2023
Last updated Nov 12, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.049%
(20th percentile)

Weaknesses

CVE ID

CVE-2023-40577

GHSA ID

GHSA-v86x-5fm3-5p7j

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.