{"answers":{"affected":"2 open source packages ship an affected version, including pterodactyl/panel.","exploited":"There is no known exploitation of CVE-2024-49762 in the wild and no public exploit code.","fix":"Upgrade pterodactyl/panel to 1.11.8 or later.","what":"CVE-2024-49762 is a medium-severity vulnerability in pterodactyl panel, published on 24 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-49762 and fix it if it is affected.\n\nWhat it is: CVE-2024-49762 is a medium-severity vulnerability in pterodactyl panel, published on 24 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-49762 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pterodactyl/panel (Packagist): affected all versions; fixed in 1.11.8\n- pterodactyl/panel (Packagist): affected all versions; fixed in 1.11.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-49762/ (Markdown: https://insights.sbomify.com/CVE-2024-49762/index.md)","id":"CVE-2024-49762","markdown":"https://insights.sbomify.com/CVE-2024-49762/index.md","name":"CVE-2024-49762","record":{"aliases":["GHSA-c479-wq8g-57hr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Game server management panel","requires_auth":"high_privilege","summary":"Attackers with log access can steal user passwords logged in plain text during 2FA disablement, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-313","name":"Cleartext Storage in a File or on Disk"}],"description":"Pterodactyl is a free, open-source game server management panel. 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. Prior to version 1.11.8, 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. This problem has been patched in version 1.11.8. 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 web servers or Layer 7 proxies. Updating to `v1.11.8` or adding the linked patch manually are the only ways to avoid this problem. 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 their account swill be compromised by this vulnerability, it's not impossible. Panel administrators should consider clearing any access logs that may contain sensitive data.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Pterodactyl Panel has plain-text logging of user passwords when two-factor authentication is disabled","id":"CVE-2024-49762","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"PlexRipper allows API leak due to open CORS policy","id":"CVE-2024-49763"},"packages":[{"ecosystem":"Packagist","fixed":["1.11.8"],"introduced":["0"],"last_affected":[],"package":"pterodactyl/panel","purl":null,"source":"GHSA-c479-wq8g-57hr"},{"ecosystem":"Packagist","fixed":["1.11.8"],"introduced":["0"],"last_affected":[],"package":"pterodactyl/panel","purl":"pkg:composer/pterodactyl/panel","source":"GHSA-c479-wq8g-57hr"}],"prev":{"headline":"REXML ReDoS vulnerability","id":"CVE-2024-49761"},"products":["panel"],"published":"2024-10-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-25","vendors":["pterodactyl"]},"summary":"Attackers with log access can steal user passwords logged in plain text during 2FA disablement, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2024-49762/"}