thelounge may publicly disclose of all usernames/idents via port 113
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
Per RFC 1413, The unique identifying tuple includes not only the ports, but also the both addresses. Without the addresses, the information becomes both non-unique and public: - If multiple connections happen to use the same local port number (which is possible if the addresses differ), the username of the first is returned for all, resulting in the wrong ident for all but the first. - By not checking the connection address, the information becomes public. Because there is only a relatively small number of local ports, and the remote ports are likely to be either 6667 or 6697, it becomes trivial to scan the entire range to get a list of idents. To prevent this from happening, disable identd or upgrade to a non vulnerable version.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | thelounge (npm) | up to 4.4.3 | — | No fix listed | GHSA-g49q-jw42-6x85 |
- thelounge (npm) Vendor— Affected up to 4.4.3 Fixed in — No fix listed GHSA-g49q-jw42-6x85
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-g49q-jw42-6x85
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences