# CVE-2019-3694: Local privilege escalation from munin to root in the packaging of munin

> Local attackers can escalate privileges from the munin user to root via a symlink following vulnerability in the munin package.

- **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:** No
- **Published:** 24 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w24q-f35x-3g4m

## What is CVE-2019-3694?

CVE-2019-3694 is a high-severity vulnerability in openSUSE Factory, published on 24 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Symbolic Link (Symlink) Following vulnerability in the packaging of munin in openSUSE Factory, Leap 15.1 allows local attackers to escalate from user munin to root. This issue affects: openSUSE Factory munin version 2.0.49-4.2 and prior versions. openSUSE Leap 15.1 munin version 2.0.40-lp151.1.1 and prior versions.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2019-3694?

It affects 2 products.


Products: Opensuse Munin, Suse Munin.

## How do I fix CVE-2019-3694?

No fix has been published for CVE-2019-3694 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-3694 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3694 and fix it if it is affected.

What it is: CVE-2019-3694 is a high-severity vulnerability in openSUSE Factory, published on 24 Jan 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-2019-3694 in the wild and no public exploit code.

Affected product: openSUSE Factory. 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-3694/ (Markdown: https://insights.sbomify.com/CVE-2019-3694/index.md)
```

## Sources

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

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