# CVE-2019-19451: Denial of service in n/a

> An attacker can cause a denial of service by providing a filename with invalid encoding, leading to an endless loop and disk exhaustion.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-19451, GHSA-4vq3-2rwv-w7mg, MGASA-2020-0022, SUSE-SU-2019:3390-1, SUSE-SU-2019:3391-1, UBUNTU-CVE-2019-19451, openSUSE-SU-2020:0021-1

## What is CVE-2019-19451?

CVE-2019-19451 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 29 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When GNOME Dia before 2019-11-27 is launched with a filename argument that is not a valid codepoint in the current encoding, it enters an endless loop, thus endlessly writing text to stdout. If this launch is from a thumbnailer service, this output will usually be written to disk via the system's logging facility (potentially with elevated privileges), thus filling up the disk and eventually rendering the system unusable. (The filename can be for a nonexistent file.) NOTE: this does not affect an upstream release, but affects certain Linux distribution packages with version numbers such as 0.97.3.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dia` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 0.97.3-17.4.1 |
| `dia` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 0.97.3-17.4.1 |
| `dia` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 0.97.3-17.4.1 |
| `dia` | SUSE:Linux Enterprise Workstation Extension 12 SP4 | All versions | 0.97.3-17.4.1 |
| `dia` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 0.97.3-17.4.1 |
| `dia` | SUSE:Linux Enterprise Workstation Extension 15 | All versions | 0.97.3-4.3.3 |
| `dia` | SUSE:Linux Enterprise Workstation Extension 15 SP1 | All versions | 0.97.3-4.3.3 |
| `dia` | openSUSE:Leap 15.1 | All versions | 0.97.3-lp151.4.3.1 |

Products: Fedoraproject Fedora, Gnome Dia, Opensuse Leap.

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

Apply the vendor's patch.

## Is CVE-2019-19451 being exploited?

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

## 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-19451 and fix it if it is affected.

What it is: CVE-2019-19451 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 29 Nov 2019. 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-19451 in the wild and no public exploit code.

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-19451/ (Markdown: https://insights.sbomify.com/CVE-2019-19451/index.md)
```

## Sources

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

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