CVE-2017-11506
HighSummary
Nessus 6.x before version 6.11 does not verify the manager's TLS certificate when making the initial outgoing connection. This could allow man-in-the-middle attacks.
Risk Assessment
The lack of TLS certificate verification poses a risk of communication interception by unauthorized parties, potentially leading to the exposure of sensitive data.
Recommendation
It is recommended to upgrade Nessus to version 6.11 or later to ensure the verification of the manager's TLS certificate.
Other vulnerabilities in Nessus 6.x
See all- CVE-2017-7850High
Nessus 6.10.x before 6.10.5 was found to be vulnerable to a local privilege escalation issue due to insecure permissions when running in Agent Mode.
- CVE-2017-7199High
Nessus versions 6.6.2 to 6.10.3 contain a flaw related to insecure permissions that may allow a local attacker to escalate privileges when the software is running in Agent Mode.
- CVE-2026-57588Low
A SQL injection vulnerability in Nessus allows an attacker to craft a malicious scan result file that, when imported by a privileged user, injects malicious SQL into the scan results database, potentially enabling exfiltration of scan-result data.
- CVE-2026-57587Medium
A SQL injection vulnerability in Nessus allows a remote, unauthenticated attacker who controls reverse DNS records for a scanned host to inject malicious SQL into the scan results database, potentially enabling exfiltration of scan-result data.
- CVE-2023-3251Medium
A pass-back vulnerability exists in the Nessus application before version 10.6.0, allowing an authenticated remote attacker with administrator privileges to uncover stored SMTP credentials.
Original NVD description (English source)
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.