Account impersonation via insufficient SSH signature validation
Published Jan 31, 2025 · Updated Mar 18, 2025
Improper signature validation in SSH Communications Security PrivX 18.0 through 36.0 allows remote authenticated users to impersonate other accounts. The native SSH proxy path accepts a public-key signature without sufficiently binding it to the requesting PrivX identity. Exploitation requires an existing PrivX account and a native SSH connection through a proxy port, and grants access to SSH target hosts authorized for the impersonated account.
Summary
What happened
Improper signature validation in SSH Communications Security PrivX 18.0 through 36.0 allows remote authenticated users to impersonate other accounts. The native SSH proxy path accepts a public-key signature without sufficiently binding it to the requesting PrivX identity. Exploitation requires an existing PrivX account and a native SSH connection through a proxy port, and grants access to SSH target hosts authorized for the impersonated account.
The record
- CVE
- CVE-2024-47857
- Published
- Jan 31, 2025
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2025CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo