ghsa-c479-wq8g-57hr
Vulnerability from github
Impact
When a user disables two-factor authentication via the Panel, a DELETE
request with their current password in a query parameter will be sent. While query parameters are encrypted when using TLS, many webservers (including ones officially documented for use with Pterodactyl) will log query parameters in plain-text, storing a user's password in plain text.
If a malicious user obtains access to these logs they could potentially authenticate against a user's account; assuming they are able to discover the account's email address or username separately.
Patches
This problem has been patched by https://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1 on the 1.0-develop
branch and released under v1.11.8
as a single commit on top of v1.11.7
https://github.com/pterodactyl/panel/commit/75b59080e2812ced677dab516222b2a3bb34e3a4
Patch file: https://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1.patch
Workarounds
There are no workarounds at this time. There is not a direct vulnerability within the software as it relates to logs generated by intermediate components such as webservers or Layer 7 proxies.
Updating to v1.11.8
or adding the linked patch manually are the only ways to avoid this problem.
User Notice
As this vulnerability relates to historical logging of sensitive data, users who have ever disabled 2FA on a Panel (self-hosted or operated by a company) should change their passwords and consider enabling 2FA if it was left disabled. While it's unlikely that your account will be compromised by this vulnerability, it's not impossible.
Panel administrators should consider clearing any access logs that may contain sensitive data, for Panels using NGINX, the access log is located at /var/log/nginx/pterodactyl.app-access.log
.
{ "affected": [ { "package": { "ecosystem": "Packagist", "name": "pterodactyl/panel" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "1.11.8" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-49762" ], "database_specific": { "cwe_ids": [ "CWE-313" ], "github_reviewed": true, "github_reviewed_at": "2024-10-24T19:07:03Z", "nvd_published_at": "2024-10-24T22:15:04Z", "severity": "MODERATE" }, "details": "### Impact\n\nWhen a user disables two-factor authentication via the Panel, a `DELETE` request with their current password in a query parameter will be sent. While query parameters are encrypted when using TLS, many webservers (including ones officially documented for use with Pterodactyl) will log query parameters in plain-text, storing a user\u0027s password in plain text.\n\nIf a malicious user obtains access to these logs they could *potentially* authenticate against a user\u0027s account; assuming they are able to discover the account\u0027s email address or username **separately**.\n\n### Patches\n\nThis problem has been patched by \u003chttps://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1\u003e on the `1.0-develop` branch and released under `v1.11.8` as a single commit on top of `v1.11.7` \u003chttps://github.com/pterodactyl/panel/commit/75b59080e2812ced677dab516222b2a3bb34e3a4\u003e\n\nPatch file: \u003chttps://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1.patch\u003e\n\n### Workarounds\n\nThere are no workarounds at this time. There is not a direct vulnerability within the software as it relates to logs generated by intermediate components such as webservers or Layer 7 proxies.\n\nUpdating to `v1.11.8` or adding the linked patch manually are the only ways to avoid this problem.\n\n### User Notice\n\nAs this vulnerability relates to historical logging of sensitive data, users who have ever disabled 2FA on a Panel (self-hosted or operated by a company) should change their passwords and consider enabling 2FA if it was left disabled. While it\u0027s unlikely that your account will be compromised by this vulnerability, it\u0027s not impossible.\n\nPanel administrators should consider clearing any access logs that may contain sensitive data, for Panels using NGINX, the access log is located at `/var/log/nginx/pterodactyl.app-access.log`.", "id": "GHSA-c479-wq8g-57hr", "modified": "2024-10-25T16:47:19Z", "published": "2024-10-24T19:07:03Z", "references": [ { "type": "WEB", "url": "https://github.com/pterodactyl/panel/security/advisories/GHSA-c479-wq8g-57hr" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49762" }, { "type": "WEB", "url": "https://github.com/pterodactyl/panel/commit/75b59080e2812ced677dab516222b2a3bb34e3a4" }, { "type": "WEB", "url": "https://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1" }, { "type": "PACKAGE", "url": "https://github.com/pterodactyl/panel" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ], "summary": "Pterodactyl Panel has plain-text logging of user passwords when two-factor authentication is disabled" }
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.