[MINOR] No rate limiting on IPC connections #29

New issue

Open

opened 2026-05-11 10:52:02 +00:00 by thabeta · 1 comment

thabeta commented

2026-05-11 10:52:02 +00:00

Owner

Problem

The IPC server spawns a new tokio::spawn for every incoming connection with no limit. A malicious or buggy client could open thousands of concurrent connections, exhausting memory and file descriptors.

Impact

Potential denial of service through resource exhaustion.

Files

crates/my_init_server/src/ipc.rs -- run_ipc_server connection loop

Suggested Fix

Add a maximum concurrent connections limit
Track connections in a semaphore or counter
Reject new connections when at capacity

## Problem The IPC server spawns a new `tokio::spawn` for every incoming connection with no limit. A malicious or buggy client could open thousands of concurrent connections, exhausting memory and file descriptors. ## Impact Potential denial of service through resource exhaustion. ## Files - `crates/my_init_server/src/ipc.rs` -- `run_ipc_server` connection loop ## Suggested Fix - Add a maximum concurrent connections limit - Track connections in a semaphore or counter - Reject new connections when at capacity

thabeta added the

enhancement

label

2026-05-11 10:53:00 +00:00

salmaelsoly commented

2026-05-11 13:36:08 +00:00

Member

Classification: valid-bug — no rate limiting on IPC connections; a malicious client can exhaust memory and FDs by opening thousands of concurrent connections.

Per issue description referencing crates/my_init_server/src/ipc.rs: tokio::spawn for every connection with no limit. No semaphore or max-connections check.

> Classification: valid-bug — no rate limiting on IPC connections; a malicious client can exhaust memory and FDs by opening thousands of concurrent connections. Per issue description referencing crates/my_init_server/src/ipc.rs: tokio::spawn for every connection with no limit. No semaphore or max-connections check.