GHSA-jpv7-p47h-f43jMedium

letmein connection limiter allows an arbitrary amount of simultaneous connections

Published
June 23, 2025
Last Modified
June 27, 2025

🔗 CVE IDs covered (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.

Severity:

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.

🎯 Affected products2

  • rust/letmeind:<= 10.2.0
  • rust/letmeinfwd:<= 10.2.0

🔗 References (4)