# CVE-2019-10143: Privilege escalation in freeradius > A local attacker with radiusd user access can escalate privileges to root by exploiting a logrotate misconfiguration in FreeRADIUS. - **Severity:** Medium 6.4 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 May 2019 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2019-10143, DEBIAN-CVE-2019-10143, GHSA-5x22-w79m-34gq, RHSA-2019:3353, UBUNTU-CVE-2019-10143 ## What is CVE-2019-10143? CVE-2019-10143 is a medium-severity vulnerability in Fedoraproject Fedora, published on 24 May 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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." Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-266 (Incorrect Privilege Assignment), CWE-250 (Execution with Unnecessary Privileges) ## Which versions are affected by CVE-2019-10143? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `freeradius` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-doc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-krb5` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-krb5-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-ldap` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-ldap-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-mysql` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-mysql-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-perl` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-perl-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-postgresql` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-postgresql-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-rest` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-rest-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-sqlite` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-sqlite-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-unixODBC` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-unixODBC-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-utils` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | | `freeradius-utils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.0.17-6.module+el8.1.0+3392+9bd8939b | Products: Fedoraproject Fedora, Freeradius Freeradius, Redhat Enterprise Linux. ## How do I fix CVE-2019-10143? Apply the vendor's patch. ## Is CVE-2019-10143 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-10143 exists. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10143 and fix it if it is affected. What it is: CVE-2019-10143 is a medium-severity vulnerability in Fedoraproject Fedora, published on 24 May 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-10143 exists. Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-10143/ (Markdown: https://insights.sbomify.com/CVE-2019-10143/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10143 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10143 - OSV: https://osv.dev/vulnerability/CVE-2019-10143 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10143/ Summaries are generated and may contain mistakes; the official description above is the record.