When installing Nessus to a directory outside of the default location, Nessus versions prior to 7.0.3 did not enforce secure permissions for sub-directories. This could allow for local privilege escalation if users had not secured the directories in the installation location.
References
Link | Resource |
---|---|
http://www.securitytracker.com/id/1040557 | Third Party Advisory VDB Entry |
https://www.tenable.com/security/tns-2018-01 | Vendor Advisory |
http://www.securitytracker.com/id/1040557 | Third Party Advisory VDB Entry |
https://www.tenable.com/security/tns-2018-01 | Vendor Advisory |
Configurations
History
21 Nov 2024, 03:59
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.securitytracker.com/id/1040557 - Third Party Advisory, VDB Entry | |
References | () https://www.tenable.com/security/tns-2018-01 - Vendor Advisory |
Information
Published : 2018-03-20 18:29
Updated : 2024-11-21 03:59
NVD link : CVE-2018-1141
Mitre link : CVE-2018-1141
CVE.ORG link : CVE-2018-1141
JSON object : View
Products Affected
tenable
- nessus
CWE
CWE-732
Incorrect Permission Assignment for Critical Resource