Security readout for executives and security teams
Plain-English summary
CVE-2021-32699 lets a malicious Pterodactyl user on affected Wings nodes consume more server resources than intended. On shared game-hosting hardware, this can degrade other customers and eventually make the physical server stop responding. The vendor fix is Wings 1.4.4.
Executive priority
Treat this as a service availability risk for shared hosting infrastructure. Patch promptly where customers or tenants share hardware; urgency is lower for isolated, trusted single-user deployments.
Technical view
Pterodactyl Wings before 1.4.4 defines improper process limits for Docker containers it creates. A low-privileged local user can trigger resource exhaustion, mapped to CWE-400, with high availability impact and no confidentiality or integrity impact stated in the sources.
Likely exposure
Exposure is limited to environments running Pterodactyl Wings versions before 1.4.4, especially shared or multi-tenant game hosting nodes where users can run managed servers on the same hardware.
Exploitation context
The source bundle does not show KEV listing or active exploitation. The CVSS vector indicates local access with low privileges, no user interaction, changed scope, and high availability impact.
Researcher notes
The strongest evidence is the GitHub advisory and associated fix reference. Sources state no non-code workaround for impacted versions, except manually setting PID limits in customized software. Do not assume remote exploitation or data compromise from the provided evidence.
Mitigation direction
- Upgrade Pterodactyl Wings to version 1.4.4 or later.
- For customized Wings deployments, manually set PID limits for created containers.
- Prioritize shared hardware hosting untrusted or semi-trusted game server users.
- Check current vendor guidance before applying nonstandard mitigations.
Validation and detection
- Inventory all Wings nodes and confirm installed versions are at least 1.4.4.
- Review customized Wings builds for explicit container PID limits.
- Check Docker container settings created by Wings for process limit enforcement.
- Review monitoring for historical process exhaustion or host unresponsiveness on affected nodes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32699 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H24Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pterodactyl/wings/security/advisories/GHSA-jj6m-r8jc-2gp7CVE reference · x_refsource_CONFIRM
- https://github.com/pterodactyl/wings/commit/e0078eee0a71d61573a94c75e6efcad069d78de3CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.