Allocation of Resources Without Limits or Throttling in websockets - #VU158593

Vulnerability details

The vulnerability allows a remote attacker to cause a denial of service by exhausting process memory.

The vulnerability exists due to allocation of resources without limits in websockets message reassembly when receiving an unfinished fragmented message through recv(). Payload-size limits do not account for zero-length fragments, and frame objects accumulate outside the flow-controlled queue. A remote attacker can start a fragmented message and continuously send valid zero-length, non-final continuation frames to exhaust memory in a receiving server or in a client connected to an attacker-controlled server.

Affected software

Remediation

External References

• https://github.com/python-websockets/websockets/security/advisories/GHSA-6m5v-9gmr-5665

Related Security Bulletins

• Allocation of Resources Without Limits or Throttling in websockets