Horizon Alert
Summary of the vulnerability and why it matters
A vulnerability exists in the Wings server control plane for Pterodactyl, an open-source game server management panel. This flaw allows a low-privileged user to access sensitive configuration details, including authentication tokens and registry information, from the daemon's full configuration. While this issue is fixed in version 1.12.3, its potential impact on the confidentiality and integrity of system credentials necessitates a review of relevant deployments.
- Sensitive credentials can be exposed.
- Confirms exposure of critical system tokens.
- Assess relevance and exposure of Pterodactyl Wings.
Attack Path
How an attacker could exploit the issue
An attacker with low privileges could exploit this vulnerability by crafting a malicious egg configuration file. This file, when processed by the Wings server control plane, would allow the attacker to access sensitive configuration details, such as authentication tokens and registry credentials. Such access could potentially lead to further compromise of the game server management panel.
- Low-privileged user access required.
- Malicious egg configuration triggers leak.
- Sensitive credential exposure risk.
Live Threat
Current exploitation, exposure, and threat context
A low-privileged user could potentially read sensitive configuration details, including authentication tokens and Docker registry information, from the Wings server control plane when specific placeholders are present in egg configuration files. This exposure could occur when these configuration files are processed, potentially impacting the integrity of the Pterodactyl server management system.
- Server configuration data could be read.
- Exposure through egg configuration placeholders.
- Compromised authentication tokens and registry access.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Wings server control plane is affected by a vulnerability that allows low-privileged users to access sensitive configuration data. This impacts organizations using Pterodactyl for game server management. The first step is to identify all Pterodactyl installations, determine their reachability and business criticality, and locate the accountable owner to plan remediation.
- Application owners should own the issue.
- Verify Pterodactyl installation reachability.
- Plan remediation based on exposure risk.