# CVE-2020-8019: syslog-ng: Local privilege escalation from new to root in %post

> Local attackers can escalate privileges to root via symlink following in syslog-ng package installation scripts on SUSE Linux.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4j55-xp84-jjv2, SUSE-SU-2020:1221-1, SUSE-SU-2020:14369-1

## What is CVE-2020-8019?

CVE-2020-8019 is a high-severity vulnerability in SUSE Linux Enterprise Debuginfo 11-SP3, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of syslog-ng of SUSE Linux Enterprise Debuginfo 11-SP3, SUSE Linux Enterprise Debuginfo 11-SP4, SUSE Linux Enterprise Module for Legacy Software 12, SUSE Linux Enterprise Point of Sale 11-SP3, SUSE Linux Enterprise Server 11-SP4-LTSS, SUSE Linux Enterprise Server for SAP 12-SP1; openSUSE Backports SLE-15-SP1, openSUSE Leap 15.1 allowed local attackers controlling the user news to escalate their privileges to root. This issue affects: SUSE Linux Enterprise Debuginfo 11-SP3 syslog-ng versions prior to 2.0.9-27.34.40.5.1. SUSE Linux Enterprise Debuginfo 11-SP4 syslog-ng versions prior to 2.0.9-27.34.40.5.1. SUSE Linux Enterprise Module for Legacy Software 12 syslog-ng versions prior to 3.6.4-12.8.1. SUSE Linux Enterprise Point of Sale 11-SP3 syslog-ng versions prior to 2.0.9-27.34.40.5.1. SUSE Linux Enterprise Server 11-SP4-LTSS syslog-ng versions prior to 2.0.9-27.34.40.5.1. SUSE Linux Enterprise Server for SAP 12-SP1 syslog-ng versions prior to 3.6.4-12.8.1. openSUSE Backports SLE-15-SP1 syslog-ng versions prior to 3.19.1-bp151.4.6.1. openSUSE Leap 15.1 syslog-ng versions prior to 3.19.1-lp151.3.6.1.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2020-8019?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `syslog-ng` | SUSE:Linux Enterprise Module for Legacy 12 | All versions | 3.6.4-12.8.1 |
| `syslog-ng` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 2.0.9-27.34.40.5.1 |
| `syslog-ng` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 2.0.9-27.34.40.5.1 |
| `syslog-ng` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 3.6.4-12.8.1 |

Products: Oneidentity Syslog-Ng.

## How do I fix CVE-2020-8019?

Apply the vendor's patch.

## Is CVE-2020-8019 being exploited?

There is no known exploitation of CVE-2020-8019 in the wild and no public exploit code.

## Other vulnerabilities in SUSE Linux Enterprise Debuginfo 11-SP3

- [CVE-2008-5110](https://insights.sbomify.com/CVE-2008-5110/): Other in n/a (critical 9.3)
- [CVE-2022-38725](https://insights.sbomify.com/CVE-2022-38725/): Integer overflow in n/a (high 7.5)
- [CVE-2002-1200](https://insights.sbomify.com/CVE-2002-1200/): Memory corruption in n/a (high 7.5)
- [CVE-2011-0343](https://insights.sbomify.com/CVE-2011-0343/): Misconfiguration in n/a (medium 6.9)
- [CVE-2011-1951](https://insights.sbomify.com/CVE-2011-1951/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8019 and fix it if it is affected.

What it is: CVE-2020-8019 is a high-severity vulnerability in SUSE Linux Enterprise Debuginfo 11-SP3, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8019 in the wild and no public exploit code.

Affected product: SUSE Linux Enterprise Debuginfo 11-SP3. 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-2020-8019/ (Markdown: https://insights.sbomify.com/CVE-2020-8019/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8019
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8019
- OSV: https://osv.dev/vulnerability/CVE-2020-8019

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-8019/
Summaries are generated and may contain mistakes; the official description above is the record.