# CVE-2020-8024: Problematic permissions in hylafax+ packaging allow escalation from uucp to other users

> Local attackers can escalate privileges from the uucp user to other users due to incorrect default permissions in the hylafax+ package.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rv88-x9wr-52g7, UBUNTU-CVE-2020-8024, openSUSE-SU-2020:0958-1

## What is CVE-2020-8024?

CVE-2020-8024 is a medium-severity vulnerability in openSUSE Factory, published on 29 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A Incorrect Default Permissions vulnerability in the packaging of hylafax+ of openSUSE Leap 15.2, openSUSE Leap 15.1, openSUSE Factory allows local attackers to escalate from user uucp to users calling hylafax binaries. This issue affects: openSUSE Leap 15.2 hylafax+ versions prior to 7.0.2-lp152.2.1. openSUSE Leap 15.1 hylafax+ version 5.6.1-lp151.3.7 and prior versions. openSUSE Factory hylafax+ versions prior to 7.0.2-2.1.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hylafax+` | openSUSE:Leap 15.1 | All versions | 7.0.2-lp151.4.3.1 |

Products: Opensuse Hylafax\+.

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

Upgrade to a fixed version.

## Is CVE-2020-8024 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8024 is a medium-severity vulnerability in openSUSE Factory, published on 29 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-8024 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-2020-8024/ (Markdown: https://insights.sbomify.com/CVE-2020-8024/index.md)
```

## Sources

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

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