Skip to content

Connection limiter is not effective and allows an arbitrary amount of simultaneous connections

Low
mbuesch published GHSA-jpv7-p47h-f43j Jun 22, 2025

Package

cargo letmeind (Rust)

Affected versions

<= 10.2.0

Patched versions

10.2.1
cargo letmeinfwd (Rust)
<= 10.2.0
10.2.1

Description

Impact

The connection limiter is implemented incorrectly.
It allows an arbitrary amount of simultaneously incoming connections (TCP, UDP and Unix socket) for the services letmeind and letmeinfwd.
Therefore, the command line option num-connections is not effective and does not limit the number of simultaneously incoming connections.

letmeind is the public network facing daemon (TCP/UDP).

letmeinfwd is the internal firewall daemon that only listens on local Unix socket.

Possible Denial Of Service by resource exhaustion.

Affected versions

All versions <= 10.2.0 are affected.

Patches

All users shall upgrade to version 10.2.1.

Workarounds

Untested possible workarounds:

  • It might be possible to limit the number of active connections to the letmeind port (default 5800) via firewall.
  • The resource consumption of the service might be restricted with a service manager such as systemd.

References

43207cd

Severity: Low

If a (D)DoS is run against the service, something is going to be affected.
The connection limiter assures that the effect on the system itself is limited at the expense of the effect on the letmein services itself.
So even with the connection limiter active, a (D)DoS can lead to a less responsive or unresponsive letmein service.

Severity

Low

CVE ID

CVE-2025-52570

Weaknesses

No CWEs