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 product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
| Link | Tags |
|---|---|
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TKODLHHUOVAYENTBP4D3N25ST3Q6LJBP/ | vendor advisory |
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/A6VKBZAZKJP5QKXDXRKCM2ZPZND3TFAX/ | vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:3353 | third party advisory vendor advisory |
| http://seclists.org/fulldisclosure/2019/Nov/14 | mailing list exploit third party advisory |
| https://freeradius.org/security/ | third party advisory |
| http://packetstormsecurity.com/files/155361/FreeRadius-3.0.19-Logrotate-Privilege-Escalation.html | exploit vdb entry third party advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10143 | issue tracking third party advisory |
| https://github.com/FreeRADIUS/freeradius-server/pull/2666 | third party advisory |