How severe is GHSA-g49q-jw42-6x85?

No CVSS score has been assigned to GHSA-g49q-jw42-6x85 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g49q-jw42-6x85?

GHSA-g49q-jw42-6x85 affects the following packages: thelounge (npm). Ecosystems affected: npm.

How do I fix GHSA-g49q-jw42-6x85?

The records we use list no patched version of thelounge for GHSA-g49q-jw42-6x85. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-g49q-jw42-6x85 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thelounge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g49q-jw42-6x85 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-g49q-jw42-6x85 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g49q-jw42-6x85 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g49q-jw42-6x85 published, and has it been updated?

GHSA-g49q-jw42-6x85 was published on May 9, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

thelounge may publicly disclose of all usernames/idents via port 113GHSA-g49q-jw42-6x85

Fix: thelounge/thelounge#4872

GHSA-g49q-jw42-6x85 is a security vulnerability in thelounge. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

May 9, 2024

Updated

May 9, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of May 9, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

15other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

theloungenpm

2Kdownloads / week

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`thelounge`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thelounge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of thelounge for GHSA-g49q-jw42-6x85. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 trivi

O3 Security · Impact-Aware SCA

Is GHSA-g49q-jw42-6x85 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works