Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

thelounge may publicly disclose of all usernames/idents via port 113

GHSA-g49q-jw42-6x85

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm thelounge

    Affected
    <= 4.4.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-g49q-jw42-6x85

  2. Revision 1 · created ·

    Published from osv record GHSA-g49q-jw42-6x85

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-g49q-jw42-6x85

Advisory: thelounge may publicly disclose of all usernames/idents via port 113
IDs: GHSA-g49q-jw42-6x85
Record: https://patchnext.com/advisories/ghsa-g49q-jw42-6x85 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm thelounge: affected <= 4.4.3

## Suggested inspection (read-only)
- `npm ls thelounge --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on thelounge.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g49q-jw42-6x85 (OSV record GHSA-g49q-jw42-6x85 lists affected ranges: npm thelounge >=0 <=4.4.3)
- Verified: https://github.com/advisories/GHSA-g49q-jw42-6x85 (GitHub-reviewed advisory GHSA-g49q-jw42-6x85 lists affected ranges: npm thelounge >=0 <=4.4.3)

Commands are suggestions: review each one before running it.

Loading voting…