CISOfy Lynis before 3.0.0 has Incorrect Access Control because of a TOCTOU race condition. The routine to check the log and report file permissions was not working as intended and could be bypassed locally. Because of the race, an unprivileged attacker can set up a log and report file, and control that up to the point where the specific routine is doing its check. After that, the file can be removed, recreated, and used for additional attacks.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - CISOfy Lynis before 3.0.0 has Incorrect Access Control because of a TOCTOU race condition. The routine to     check the log and report file permissions was not working as intended and could be bypassed locally.
    Because of the race, an unprivileged attacker can set up a log and report file, and control that up to the     point where the specific routine is doing its check. After that, the file can be removed, recreated, and     used for additional attacks. (CVE-2020-13882)

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of lynis installed on the remote host is prior to 3.0.0-1.17. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS-2020-1419 advisory.

    In CISOfy Lynis 2.x through 2.7.5, the license key can be obtained by looking at the process list when a     data upload is being performed. This license can be used to upload data to a central Lynis server.
    Although no data can be extracted by knowing the license key, it may be possible to upload the data of     additional scans. (CVE-2019-13033)For additional     information:https://nvd.nist.gov/vuln/detail/cve-2019-13033

    CISOfy Lynis before 3.0.0 has Incorrect Access Control because of a TOCTOU race condition. The routine to     check the log and report file permissions was not working as intended and could be bypassed locally.
    Because of the race, an unprivileged attacker can set up a log and report file, and control that up to the     point where the specific routine is doing its check. After that, the file can be removed, recreated, and     used for additional attacks. (CVE-2020-13882)For additional     information:https://nvd.nist.gov/vuln/detail/cve-2020-13882

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Update to 3.0.0 (rhbz #1848716), fixes CVE-2020-13882 / CVE-2019-13033

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Update to 3.0.0 (rhbz #1848716), Fixes CVE-2020-13882 / CVE-2019-13033

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
258530	Linux Distros Unpatched Vulnerability : CVE-2020-13882	Nessus	Misc.	medium
140091	Amazon Linux AMI : lynis (ALAS-2020-1419)	Nessus	Amazon Linux Local Security Checks	medium
137929	Fedora 32 : lynis (2020-f251753b0f)	Nessus	Fedora Local Security Checks	medium
137921	Fedora 31 : lynis (2020-059e1591d6)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2020-13882

medium

Tenable Plugins

medium

medium

medium

medium