# CVE-2019-19308: Null dereference in n/a

> A NULL pointer dereference in GNOME Font Viewer allows attackers to cause a denial of service by providing a malformed TTF font file.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **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:** 27 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-19308, GHSA-xr69-7fhc-h6vj, OESA-2022-2074, UBUNTU-CVE-2019-19308

## What is CVE-2019-19308?

CVE-2019-19308 is a medium-severity vulnerability in n/a, published on 27 Nov 2019. 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

In text_to_glyphs in sushi-font-widget.c in gnome-font-viewer 3.34.0, there is a NULL pointer dereference while parsing a TTF font file that lacks a name section (due to a g_strconcat call that returns NULL).

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Gnome Gnome-Font-Viewer.

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

Apply the vendor's patch.

## Is CVE-2019-19308 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19308 is a medium-severity vulnerability in n/a, published on 27 Nov 2019. 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-2019-19308 in the wild and no public exploit code.

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

## Sources

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

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