First published: Wed Aug 09 2017(Updated: )
When linking a Nessus scanner or agent to Tenable.io or other manager, Nessus 6.x before 6.11 does not verify the manager's TLS certificate when making the initial outgoing connection. This could allow man-in-the-middle attacks.
Credit: vulnreport@tenable.com
Affected Software | Affected Version | How to fix |
---|---|---|
Tenable Nessus | =6.0.0 | |
Tenable Nessus | =6.0.1 | |
Tenable Nessus | =6.0.2 | |
Tenable Nessus | =6.1.0 | |
Tenable Nessus | =6.1.1 | |
Tenable Nessus | =6.1.2 | |
Tenable Nessus | =6.2.0 | |
Tenable Nessus | =6.2.1 | |
Tenable Nessus | =6.3.0 | |
Tenable Nessus | =6.3.1 | |
Tenable Nessus | =6.3.2 | |
Tenable Nessus | =6.3.3 | |
Tenable Nessus | =6.3.4 | |
Tenable Nessus | =6.3.5 | |
Tenable Nessus | =6.3.6 | |
Tenable Nessus | =6.3.7 | |
Tenable Nessus | =6.4.0 | |
Tenable Nessus | =6.4.1 | |
Tenable Nessus | =6.4.2 | |
Tenable Nessus | =6.4.3 | |
Tenable Nessus | =6.5.0 | |
Tenable Nessus | =6.5.1 | |
Tenable Nessus | =6.5.2 | |
Tenable Nessus | =6.5.3 | |
Tenable Nessus | =6.5.4 | |
Tenable Nessus | =6.5.5 | |
Tenable Nessus | =6.5.6 | |
Tenable Nessus | =6.6.0 | |
Tenable Nessus | =6.6.1 | |
Tenable Nessus | =6.6.2 | |
Tenable Nessus | =6.7.0 | |
Tenable Nessus | =6.8.0 | |
Tenable Nessus | =6.8.1 | |
Tenable Nessus | =6.9.0 | |
Tenable Nessus | =6.9.1 | |
Tenable Nessus | =6.9.2 | |
Tenable Nessus | =6.9.3 | |
Tenable Nessus | =6.10.0 | |
Tenable Nessus | =6.10.1 | |
Tenable Nessus | =6.10.2 | |
Tenable Nessus | =6.10.3 | |
Tenable Nessus | =6.10.4 | |
Tenable Nessus | =6.10.5 | |
Tenable Nessus | =6.10.6 | |
Tenable Nessus | =6.10.7 | |
Tenable Nessus | =6.10.8 | |
Tenable Nessus | =6.10.9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.