According to its self-reported version, the Tenable SecurityCenter application installed on the remote host is below 6.0.0 and is therefore affected by multiple vulnerabilities:
    
    - curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a       non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to       the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this       request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443       for HTTPS) and instead return a non-200 status code to the client. Due to flaws in the error/cleanup       handling, this could trigger a double free in curl if one of the following schemes were used in the       URL for the transfer: dict, gopher, gophers, ldap, ldaps, rtmp, rtmps, or telnet. The earliest       affected version is 7.77.0.(CVE-2022-42915)

    - A LDAP injection vulnerability exists in Tenable.sc due to improper validation of user-supplied input       before returning it to users. An authenticated attacker could generate data in Active Directory using       the application account through blind LDAP injection. (CVE-2023-0476)

    - A formula injection vulnerability exists in Tenable.sc due to improper validation of user-supplied input       before returning it to users. An authenticated attacker could leverage the reporting system to export       reports containing formulas, which would then require a victim to approve and execute on a host.       (CVE-2023-24493)     
    - A stored cross-site scripting (XSS) vulnerability exists in Tenable.sc due to improper validation of       user-supplied input before returning it to users. An authenticated, remote attacker can exploit this by       convincing a user to click a specially crafted URL, to execute arbitrary script code in a user's browser       session. (CVE-2023-24494)

    - A Server Side Request Forgery (SSRF) vulnerability exists in Tenable.sc due to improper validation of       session & user-accessible input data. A privileged, authenticated remote attacker could interact with       external and internal services covertly. (CVE-2023-24495)

    - In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its       HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP       step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the       given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion,       e.g., using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of       U+002E (.). The earliest affected version is 7.77.0 2021-05-26. (CVE-2022-42916)   Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

Tenable SecurityCenter < 6.0.0 Multiple Vulnerabilities (TNS-2023-03)

high Nessus Plugin ID 170729

Version 1.4