letmeind
Affected
- introduced
0, fixed10.2.1(semver)
Fixed versions
10.2.1
Fix
- Fixed version
10.2.1cargo update -p letmeind --precise 10.2.1
Advisory
Also known as: CVE-2025-52570
letmein connection limiter allows an arbitrary amount of simultaneous connections
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:
letmeind port (default 5800) via firewall.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.
Medium Basis: The source's own band: MODERATE
0, fixed 10.2.1 (semver)10.2.1
10.2.1cargo update -p letmeind --precise 10.2.10, fixed 10.2.1 (semver)10.2.1
10.2.1cargo update -p letmeinfwd --precise 10.2.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0