Quick answers
- Is CVE-2024-48460 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-48460 being exploited in the wild.
- How severe is CVE-2024-48460?
- Medium severity, with a CVSS score of 4, published 17 January 2025.
- Which products and versions are affected?
- Eugeny Tabby before 1.0.214; tabby-ssh (npm) SEMVER:introduced=0,fixed=1.0.214.
- Is there a fix for CVE-2024-48460?
- Yes. tabby-ssh (npm): upgrade to 1.0.214 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-48460 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-48460?
- Check whether you run Eugeny Tabby or tabby-ssh (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- tabby-ssh (npm): upgrade to 1.0.214 or later
npm install tabby-ssh@1.0.214
Technical details
A credential disclosure vulnerability (CWE-200) in Eugeny Tabby's SSH module causes the application to transmit SSH credentials before completing host key verification. The vulnerability exists in tabby-ssh versions prior to 1.0.214. An attacker can set up a fake SSH server, which triggers the host key verification dialog; if the user proceeds to disconnect after the prompt, the credentials are sent anyway. The network-accessible nature of SSH combined with the lack of proper verification sequencing allows remote credential harvesting. Patch available in version 1.0.214 and later.
Affected products
- Eugeny Tabby before 1.0.214
Identifiers
- CVE-2024-48460
- GHSA-8vq4-8hfp-29xh
Timeline
- 2024-09-22: disclosed: Issue reported on GitHub
- 2025-01-17: advisory: GHSA-8vq4-8hfp-29xh published
- 2025-01-16: patched: Fix available in version 1.0.214