ghsa-vx57-7f4q-fpc7
Vulnerability from github
Impact
In 2.23.0, Prometheus changed its default UI to the New ui. To ensure a seamless transition, the URL's prefixed by /new redirect to /. Due to a bug in the code, it is possible for an attacker to craft an URL that can redirect to any other URL, in the /new endpoint.
If a user visits a prometheus server with a specially crafted address (e.g.: http://127.0.0.1:9090/new/new<url>), they can be redirected to an arbitrary URL.
e.g. if a user visits http://127.0.0.1:9090/new/newhttp://www.google.com/, they will be redirected to http://google.com.
Patches
The issue will be patched in 2.26.1 and 2.27.1 releases. In 2.28.0, the /new endpoint will be removed completely.
Workarounds
The workaround is to disable access to /new via a reverse proxy in front of Prometheus.
Note: Users who use a --web.external-url= flag with a path (e.g. --web.external-url=http://example.com/prometheus) are not affected.
For more information
If you have any questions or comments about this advisory, please use our community channels (https://prometheus.io/community). Our security policy is available at https://prometheus.io/docs/operating/security/
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/prometheus/prometheus"
},
"ranges": [
{
"events": [
{
"introduced": "2.23.0"
},
{
"fixed": "2.26.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/prometheus/prometheus"
},
"ranges": [
{
"events": [
{
"introduced": "2.27.0"
},
{
"fixed": "2.27.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.27.0"
]
}
],
"aliases": [
"CVE-2021-29622"
],
"database_specific": {
"cwe_ids": [
"CWE-601"
],
"github_reviewed": true,
"github_reviewed_at": "2021-05-19T17:58:51Z",
"nvd_published_at": "2021-05-19T20:15:00Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nIn 2.23.0, Prometheus changed its default UI to the New ui. To ensure a seamless transition, the URL\u0027s prefixed by /new redirect to /.\nDue to a bug in the code, it is possible for an attacker to craft an URL that can redirect to any other URL, in the /new endpoint.\n\nIf a user visits a prometheus server with a specially crafted address (e.g.: `http://127.0.0.1:9090/new/new\u003curl\u003e`), they can be redirected to an arbitrary URL.\n\ne.g. if a user visits http://127.0.0.1:9090/new/newhttp://www.google.com/, they will be redirected to http://google.com.\n\n### Patches\n\nThe issue will be patched in 2.26.1 and 2.27.1 releases.\nIn 2.28.0, the /new endpoint will be removed completely.\n\n### Workarounds\n\nThe workaround is to disable access to /new via a reverse proxy in front of Prometheus.\n\nNote: Users who use a `--web.external-url=` flag _with a path_ (e.g. `--web.external-url=http://example.com/prometheus`) are not affected.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please use our community channels (https://prometheus.io/community).\nOur security policy is available at https://prometheus.io/docs/operating/security/\n",
"id": "GHSA-vx57-7f4q-fpc7",
"modified": "2021-05-28T22:05:12Z",
"published": "2022-02-15T01:57:18Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/prometheus/prometheus/security/advisories/GHSA-vx57-7f4q-fpc7"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-29622"
},
{
"type": "WEB",
"url": "https://github.com/prometheus/prometheus/releases/tag/v2.26.1"
},
{
"type": "WEB",
"url": "https://github.com/prometheus/prometheus/releases/tag/v2.27.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Arbitrary redirects under /new endpoint"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.