Unauthenticated root login via static SSH keys
Published Nov 4, 2021 · Updated Nov 7, 2024
Use of hard-coded cryptographic keys in Cisco Policy Suite allows unauthenticated remote attackers to log in as root via SSH. The SSH authentication subsystem reuses the same static private keys across installations, allowing a key extracted from one controlled system to authenticate to another deployment. Exploitation requires network reachability to SSH and the reusable key; successful access grants root-level read, write, and service-control capability.
Summary
What happened
Use of hard-coded cryptographic keys in Cisco Policy Suite allows unauthenticated remote attackers to log in as root via SSH. The SSH authentication subsystem reuses the same static private keys across installations, allowing a key extracted from one controlled system to authenticate to another deployment. Exploitation requires network reachability to SSH and the reusable key; successful access grants root-level read, write, and service-control capability.
The record
- CVE
- CVE-2021-40119
- Published
- Nov 4, 2021
- Updated
- Nov 7, 2024
- Vendor
- ClamAV
- Product
- Cisco Policy Suite
- Classifications
- CWE-798, CWE-321, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 2021CVE publishedPublication date reported by the CVE source.
- Nov 7, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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