Skip to content

Asymmetric Resource Consumption (Amplification) in Docker containers created by Wings

Moderate severity GitHub Reviewed Published Jun 21, 2021 in pterodactyl/wings • Updated Jan 29, 2023

Package

gomod github.com/pterodactyl/wings (Go)

Affected versions

< 1.4.4

Patched versions

1.4.4

Description

Impact

All versions of Pterodactyl Wings preior to 1.4.4 are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding.

Patches

Users should upgrade to 1.4.4.

Workarounds

There is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created.

For more information

If you have any questions or comments about this advisory:

  • Contact us on Discord
  • Email us at dane ät pterodactyl dot io

References

@DaneEveritt DaneEveritt published to pterodactyl/wings Jun 21, 2021
Reviewed Jun 22, 2021
Published by the National Vulnerability Database Jun 22, 2021
Published to the GitHub Advisory Database Jun 23, 2021
Last updated Jan 29, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2021-32699

GHSA ID

GHSA-jj6m-r8jc-2gp7

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.