GHSA-7mwh-q3xm-qh6p
Vulnerability from github
6.9 (Medium) - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Summary
The /debug/querylogz
and /debug/env
pages for vtgate
and vttablet
do not properly escape user input. The result is that queries executed by Vitess can write HTML into the monitoring page at will.
Details
These pages are rendered using text/template
instead of rendering with a proper HTML templating engine.
PoC
Execute any query where part of it is HTML markup, for example as part of a string. To make it easier to observe you might want to make sure the query takes a few seconds to complete, giving you time to refresh the status page.
Example query that can trigger the issue:
sql
UPDATE users
SET
email = CONCAT("<img src=https://cataas.com/cat/says/oops>", users.idUser, "@xxx")
WHERE
email NOT LIKE '%xxx%' AND email != "demo@xxx.com"
Result:
Impact
Anyone looking at the Vitess status page is affected. This would normally be owners / administrators of the Vitess cluster.
Anyone that can influence what text show up in queries can trigger it. This would normally be pretty much everybody interacting with a system that uses Vitess as a backend.
{ "affected": [ { "package": { "ecosystem": "Go", "name": "vitess.io/vitess" }, "ranges": [ { "events": [ { "introduced": "0.21.0-rc1" }, { "fixed": "0.21.1" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "vitess.io/vitess" }, "ranges": [ { "events": [ { "introduced": "0.20.0-rc1" }, { "fixed": "0.20.4" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "vitess.io/vitess" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "0.19.8" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-53257" ], "database_specific": { "cwe_ids": [ "CWE-79" ], "github_reviewed": true, "github_reviewed_at": "2024-12-03T18:43:33Z", "nvd_published_at": "2024-12-03T16:15:23Z", "severity": "MODERATE" }, "details": "### Summary\n\nThe `/debug/querylogz` and `/debug/env` pages for `vtgate` and `vttablet` do not properly escape user input. The result is that queries executed by Vitess can write HTML into the monitoring page at will.\n\n### Details\n\nThese pages are rendered using `text/template` instead of rendering with a proper HTML templating engine.\n\n### PoC\n\nExecute any query where part of it is HTML markup, for example as part of a string. To make it easier to observe you might want to make sure the query takes a few seconds to complete, giving you time to refresh the status page. \n\nExample query that can trigger the issue:\n\n```sql\nUPDATE users\nSET\n email = CONCAT(\"\u003cimg src=https://cataas.com/cat/says/oops\u003e\", users.idUser, \"@xxx\")\nWHERE\n email NOT LIKE \u0027%xxx%\u0027 AND email != \"demo@xxx.com\"\n```\n\nResult: \n\n![image](https://github.com/user-attachments/assets/c583816b-157c-474e-bbed-152b3dc0372f)\n\n### Impact\n\nAnyone looking at the Vitess status page is affected. This would normally be owners / administrators of the Vitess cluster.\n\nAnyone that can influence what text show up in queries can trigger it. This would normally be pretty much everybody interacting with a system that uses Vitess as a backend.", "id": "GHSA-7mwh-q3xm-qh6p", "modified": "2024-12-16T15:26:04Z", "published": "2024-12-03T18:43:33Z", "references": [ { "type": "WEB", "url": "https://github.com/vitessio/vitess/security/advisories/GHSA-7mwh-q3xm-qh6p" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53257" }, { "type": "WEB", "url": "https://github.com/vitessio/vitess/commit/2b71d1b5f8ca676beeab2875525003cd45096217" }, { "type": "PACKAGE", "url": "https://github.com/vitessio/vitess" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N", "type": "CVSS_V4" } ], "summary": "Vitess allows HTML injection in /debug/querylogz \u0026 /debug/env" }
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.