Trusted-entity spoofing via improper certificate validation
Published Feb 5, 2021 · Updated Aug 4, 2024
Improper certificate validation in Tenable Nessus AMI 8.12.0 and earlier allows attackers to spoof a trusted entity from a MITM position. The affected AMI either omits certificate validation or applies it incorrectly, so an intercepted connection accepts an attacker's endpoint as trusted. Exploitation requires control of the connection path and compromises the integrity of the trusted exchange; no direct data disclosure is reported.
Summary
What happened
Improper certificate validation in Tenable Nessus AMI 8.12.0 and earlier allows attackers to spoof a trusted entity from a MITM position. The affected AMI either omits certificate validation or applies it incorrectly, so an intercepted connection accepts an attacker's endpoint as trusted. Exploitation requires control of the connection path and compromises the integrity of the trusted exchange; no direct data disclosure is reported.
The record
- CVE
- CVE-2020-5812
- Published
- Feb 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Tenable
- Product
- Nessus
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=8.12.0 and earlier
What conditions does exploitation require?
What is affected?
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