Vulnerabilities > Tenable > Nessus Agent

DATE CVE VULNERABILITY TITLE RISK
2023-11-01 CVE-2023-5847 Unspecified vulnerability in Tenable Nessus
Under certain conditions, a low privileged attacker could load a specially crafted file during installation or upgrade to escalate privileges on Windows and Linux hosts.
local
low complexity
tenable
7.3
2021-09-09 CVE-2021-20117 Unspecified vulnerability in Tenable Nessus Agent
Nessus Agent 8.3.0 and earlier was found to contain a local privilege escalation vulnerability which could allow an authenticated, local administrator to run specific executables on the Nessus Agent host.
local
low complexity
tenable
6.7
2021-09-09 CVE-2021-20118 Unspecified vulnerability in Tenable Nessus Agent
Nessus Agent 8.3.0 and earlier was found to contain a local privilege escalation vulnerability which could allow an authenticated, local administrator to run specific executables on the Nessus Agent host.
local
low complexity
tenable
6.7
2021-03-25 CVE-2021-3450 Improper Certificate Validation vulnerability in multiple products
The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain.
7.4
2021-03-19 CVE-2021-20077 Unspecified vulnerability in Tenable Nessus Agent
Nessus Agent versions 7.2.0 through 8.2.2 were found to inadvertently capture the IAM role security token on the local host during initial linking of the Nessus Agent when installed on an Amazon EC2 instance.
local
low complexity
tenable
6.7
2020-11-05 CVE-2020-5793 Unspecified vulnerability in Tenable Nessus and Nessus Agent
A vulnerability in Nessus versions 8.9.0 through 8.12.0 for Windows & Nessus Agent 8.0.0 and 8.1.0 for Windows could allow an authenticated local attacker to copy user-supplied files to a specially constructed path in a specifically named user directory.
local
low complexity
tenable
7.8
2019-09-09 CVE-2019-16168 Divide By Zero vulnerability in multiple products
In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner."
6.5