# CVE-2019-16115: Memory corruption in n/a

> A stack-based buffer under-read in Xpdf allows attackers to cause denial of service via crafted PDF files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 8 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fx8g-cgwg-pm6c, SUSE-SU-2023:3292-1, SUSE-SU-2023:3303-1, SUSE-SU-2023:3399-1, UBUNTU-CVE-2019-16115

## What is CVE-2019-16115?

CVE-2019-16115 is a high-severity memory corruption vulnerability in Glyphandcog Xpdfreader, published on 8 Sep 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 Xpdf 4.01.01, a stack-based buffer under-read could be triggered in IdentityFunction::transform in Function.cc, used by GfxAxialShading::getColor. It can, for example, be triggered by sending a crafted PDF document to the pdftoppm tool. It allows an attacker to use a crafted PDF file to cause Denial of Service or possibly unspecified other impact.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `poppler` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 0.79.0-150200.3.14.1 |
| `poppler` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 0.79.0-150200.3.14.1 |
| `poppler` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 0.43.0-16.28.1 |
| `poppler-qt` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 0.43.0-16.28.1 |
| `poppler` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 0.43.0-16.28.1 |
| `poppler-qt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 0.43.0-16.28.1 |
| `poppler` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 0.24.4-14.29.1 |
| `poppler` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 0.43.0-16.28.1 |
| `poppler-qt` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 0.43.0-16.28.1 |
| `poppler` | SUSE:Manager Proxy 4.2 | All versions | 0.79.0-150200.3.14.1 |
| `poppler` | SUSE:Manager Server 4.2 | All versions | 0.79.0-150200.3.14.1 |
| `poppler` | openSUSE:Leap 15.4 | All versions | 0.79.0-150200.3.14.1 |

Products: Glyphandcog Xpdfreader.

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

Apply the vendor's patch.

## Is CVE-2019-16115 being exploited?

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

## Other vulnerabilities in Glyphandcog Xpdfreader

- [CVE-2022-24106](https://insights.sbomify.com/CVE-2022-24106/): Integer overflow in n/a (high 7.8)
- [CVE-2022-24107](https://insights.sbomify.com/CVE-2022-24107/): Integer overflow in n/a (high 7.8)
- [CVE-2019-14288](https://insights.sbomify.com/CVE-2019-14288/): Integer overflow in n/a (high 7.8)
- [CVE-2019-13289](https://insights.sbomify.com/CVE-2019-13289/): Use after free in n/a (high 7.8)
- [CVE-2019-9587](https://insights.sbomify.com/CVE-2019-9587/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16115 is a high-severity memory corruption vulnerability in Glyphandcog Xpdfreader, published on 8 Sep 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-16115 in the wild and no public exploit code.

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

## Sources

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

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