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.
References
Link | Resource |
---|---|
http://www.securitytracker.com/id/1039141 | Third Party Advisory VDB Entry |
https://www.tenable.com/security/tns-2017-11 | Vendor Advisory |
http://www.securitytracker.com/id/1039141 | Third Party Advisory VDB Entry |
https://www.tenable.com/security/tns-2017-11 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 03:07
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.securitytracker.com/id/1039141 - Third Party Advisory, VDB Entry | |
References | () https://www.tenable.com/security/tns-2017-11 - Vendor Advisory |
Information
Published : 2017-08-09 12:29
Updated : 2024-11-21 03:07
NVD link : CVE-2017-11506
Mitre link : CVE-2017-11506
CVE.ORG link : CVE-2017-11506
JSON object : View
Products Affected
tenable
- nessus
CWE
CWE-295
Improper Certificate Validation