DoS attack against the Stork UI from an unauthenticated user
If an unauthenticated user sends a large amount of data to the Stork UI, it may cause memory and disk use problems for the system running the Stork server.
This issue affects Stork versions 1.0.0 through 2.3.0.
Resource exhaustion. A sufficiently large input will cause Stork to allocate more memory than is available, leading to the failure of the `stork-server` process and/or other processes. Repeated smaller inputs may not exhaust memory but may fill log storage or force premature log rotation.
CAPEC ID: N/A
Description: Resource exhaustion. A sufficiently large input will cause Stork to allocate more memory than is available, leading to the failure of the `stork-server` process and/or other processes. Repeated smaller inputs may not exhaust memory but may fill log storage or force premature log rotation.
Solutions
Upgrade to the patched release most closely related to your current version of Stork: 2.2.1 or 2.3.1.
Configurations
Workarounds
Placing the Stork server behind a firewall or proxy that only allows access from trusted clients, and/or enforces input size limits, is an effective workaround.
Exploits
This flaw was discovered in internal testing. We are not aware of any active exploits.