It was discovered freeradius up to and including version 3.0.19 does not correctly configure logrotate, allowing a local attacker who already has control of the radiusd user to escalate his privileges to root, by tricking logrotate into writing a radiusd-writable file to a directory normally inaccessible by the radiusd user. NOTE: the upstream software maintainer has stated "there is simply no way for anyone to gain privileges through this alleged issue."

The remote Oracle Linux 8 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2019-3353 advisory.

  - ** DISPUTED ** It was discovered freeradius up to and including version 3.0.19 does not correctly     configure logrotate, allowing a local attacker who already has control of the radiusd user to escalate his     privileges to root, by tricking logrotate into writing a radiusd-writable file to a directory normally     inaccessible by the radiusd user. NOTE: the upstream software maintainer has stated there is simply no     way for anyone to gain privileges through this alleged issue. (CVE-2019-10143)

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

The remote NewStart CGSL host, running version CORE 5.05 / MAIN 5.05, has freeradius packages installed that are affected by multiple vulnerabilities:

  - ** DISPUTED ** It was discovered freeradius up to and including version 3.0.19 does not correctly     configure logrotate, allowing a local attacker who already has control of the radiusd user to escalate his     privileges to root, by tricking logrotate into writing a radiusd-writable file to a directory normally     inaccessible by the radiusd user. NOTE: the upstream software maintainer has stated there is simply no     way for anyone to gain privileges through this alleged issue. (CVE-2019-10143)

  - In FreeRADIUS 3.0 through 3.0.19, on average 1 in every 2048 EAP-pwd handshakes fails because the password     element cannot be found within 10 iterations of the hunting and pecking loop. This leaks information that     an attacker can use to recover the password of any user. This information leakage is similar to the     Dragonblood attack and CVE-2019-9494. (CVE-2019-13456)

  - In FreeRADIUS 3.0.x before 3.0.20, the EAP-pwd module used a global OpenSSL BN_CTX instance to handle all     handshakes. This mean multiple threads use the same BN_CTX instance concurrently, resulting in crashes     when concurrent EAP-pwd handshakes are initiated. This can be abused by an adversary as a Denial-of-     Service (DoS) attack. (CVE-2019-17185)

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

The remote NewStart CGSL host, running version CORE 5.04 / MAIN 5.04, has freeradius packages installed that are affected by multiple vulnerabilities:

  - In FreeRADIUS 3.0.x before 3.0.20, the EAP-pwd module used a global OpenSSL BN_CTX instance to handle all     handshakes. This mean multiple threads use the same BN_CTX instance concurrently, resulting in crashes     when concurrent EAP-pwd handshakes are initiated. This can be abused by an adversary as a Denial-of-     Service (DoS) attack. (CVE-2019-17185)

  - ** DISPUTED ** It was discovered freeradius up to and including version 3.0.19 does not correctly     configure logrotate, allowing a local attacker who already has control of the radiusd user to escalate his     privileges to root, by tricking logrotate into writing a radiusd-writable file to a directory normally     inaccessible by the radiusd user. NOTE: the upstream software maintainer has stated there is simply no     way for anyone to gain privileges through this alleged issue. (CVE-2019-10143)

  - In FreeRADIUS 3.0 through 3.0.19, on average 1 in every 2048 EAP-pwd handshakes fails because the password     element cannot be found within 10 iterations of the hunting and pecking loop. This leaks information that     an attacker can use to recover the password of any user. This information leakage is similar to the     Dragonblood attack and CVE-2019-9494. (CVE-2019-13456)

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

The remote CentOS Linux 8 host has packages installed that are affected by a vulnerability as referenced in the CESA-2019:3353 advisory.

  - freeradius: privilege escalation due to insecure logrotate configuration (CVE-2019-10143)

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

The version of tested product installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2020-1515 advisory.

  - ** DISPUTED ** It was discovered freeradius up to and including version 3.0.19 does not correctly     configure logrotate, allowing a local attacker who already has control of the radiusd user to escalate his     privileges to root, by tricking logrotate into writing a radiusd-writable file to a directory normally     inaccessible by the radiusd user. NOTE: the upstream software maintainer has stated there is simply no     way for anyone to gain privileges through this alleged issue. (CVE-2019-10143)

  - In FreeRADIUS 3.0 through 3.0.19, on average 1 in every 2048 EAP-pwd handshakes fails because the password     element cannot be found within 10 iterations of the hunting and pecking loop. This leaks information that     an attacker can use to recover the password of any user. This information leakage is similar to the     Dragonblood attack and CVE-2019-9494. (CVE-2019-13456)

  - In FreeRADIUS 3.0.x before 3.0.20, the EAP-pwd module used a global OpenSSL BN_CTX instance to handle all     handshakes. This mean multiple threads use the same BN_CTX instance concurrently, resulting in crashes     when concurrent EAP-pwd handshakes are initiated. This can be abused by an adversary as a Denial-of-     Service (DoS) attack. (CVE-2019-17185)

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

Security Fix(es) :

  - freeradius: privilege escalation due to insecure     logrotate configuration (CVE-2019-10143)

  - freeradius: eap-pwd: Information leak due to aborting     when needing more than 10 iterations (CVE-2019-13456)

  - freeradius: eap-pwd: DoS issues due to multithreaded     BN_CTX access (CVE-2019-17185)

The remote CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2020:3984 advisory.

  - freeradius: privilege escalation due to insecure logrotate configuration (CVE-2019-10143)

  - freeradius: eap-pwd: Information leak due to aborting when needing more than 10 iterations     (CVE-2019-13456)

  - freeradius: eap-pwd: DoS issues due to multithreaded BN_CTX access (CVE-2019-17185)

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

The remote Oracle Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2020-3984 advisory.

  - ** DISPUTED ** It was discovered freeradius up to and including version 3.0.19 does not correctly     configure logrotate, allowing a local attacker who already has control of the radiusd user to escalate his     privileges to root, by tricking logrotate into writing a radiusd-writable file to a directory normally     inaccessible by the radiusd user. NOTE: the upstream software maintainer has stated there is simply no     way for anyone to gain privileges through this alleged issue. (CVE-2019-10143)

  - In FreeRADIUS 3.0 through 3.0.19, on average 1 in every 2048 EAP-pwd handshakes fails because the password     element cannot be found within 10 iterations of the hunting and pecking loop. This leaks information that     an attacker can use to recover the password of any user. This information leakage is similar to the     Dragonblood attack and CVE-2019-9494. (CVE-2019-13456)

  - In FreeRADIUS 3.0.x before 3.0.20, the EAP-pwd module used a global OpenSSL BN_CTX instance to handle all     handshakes. This mean multiple threads use the same BN_CTX instance concurrently, resulting in crashes     when concurrent EAP-pwd handshakes are initiated. This can be abused by an adversary as a Denial-of-     Service (DoS) attack. (CVE-2019-17185)

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

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:3984 advisory.

  - freeradius: privilege escalation due to insecure logrotate configuration (CVE-2019-10143)

  - freeradius: eap-pwd: Information leak due to aborting when needing more than 10 iterations     (CVE-2019-13456)

  - freeradius: eap-pwd: DoS issues due to multithreaded BN_CTX access (CVE-2019-17185)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2019:3353 advisory.

  - freeradius: privilege escalation due to insecure logrotate configuration (CVE-2019-10143)

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

According to the version of the freeradius package installed, the EulerOS installation on the remote host is affected by the following vulnerability :

  - It was discovered freeradius does not correctly     configure logrotate, allowing a local attacker who     already has control of the radiusd user to escalate his     privileges to root, by tricking logrotate into writing     a radiusd-writable file to a directory normally     inaccessible by the radiusd user.(CVE-2019-10143)

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

ID	Name	Product	Family	Severity
180877	Oracle Linux 8 : freeradius:3.0 (ELSA-2019-3353)	Nessus	Oracle Linux Local Security Checks	high
154528	NewStart CGSL CORE 5.05 / MAIN 5.05 : freeradius Multiple Vulnerabilities (NS-SA-2021-0151)	Nessus	NewStart CGSL Local Security Checks	high
147253	NewStart CGSL CORE 5.04 / MAIN 5.04 : freeradius Multiple Vulnerabilities (NS-SA-2021-0037)	Nessus	NewStart CGSL Local Security Checks	high
145657	CentOS 8 : freeradius:3.0 (CESA-2019:3353)	Nessus	CentOS Local Security Checks	high
141965	Amazon Linux 2 : freeradius (ALAS-2020-1515)	Nessus	Amazon Linux Local Security Checks	high
141703	Scientific Linux Security Update : freeradius on SL7.x x86_64 (20201001)	Nessus	Scientific Linux Local Security Checks	high
141587	CentOS 7 : freeradius (CESA-2020:3984)	Nessus	CentOS Local Security Checks	high
141233	Oracle Linux 7 : freeradius (ELSA-2020-3984)	Nessus	Oracle Linux Local Security Checks	high
141018	RHEL 7 : freeradius (RHSA-2020:3984)	Nessus	Red Hat Local Security Checks	high
130531	RHEL 8 : freeradius:3.0 (RHSA-2019:3353)	Nessus	Red Hat Local Security Checks	high
129258	EulerOS 2.0 SP3 : freeradius (EulerOS-SA-2019-2065)	Nessus	Huawei Local Security Checks	high
127000	EulerOS 2.0 SP8 : freeradius (EulerOS-SA-2019-1763)	Nessus	Huawei Local Security Checks	high
126874	EulerOS 2.0 SP2 : freeradius (EulerOS-SA-2019-1747)	Nessus	Huawei Local Security Checks	high
126416	EulerOS 2.0 SP5 : freeradius (EulerOS-SA-2019-1674)	Nessus	Huawei Local Security Checks	high

Detections

Analytics

CVE-2019-10143

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high

high

high