# CVE-2019-14250: Integer overflow in n/a

> Integer overflow in GNU libiberty leads to heap-based buffer overflow, potentially allowing code execution or denial of service.

- **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:** 24 Jul 2019
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2019-14250, GHSA-cxc9-2rq6-pr6h, SUSE-SU-2022:2015-1, UBUNTU-CVE-2019-14250

## What is CVE-2019-14250?

CVE-2019-14250 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 24 Jul 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

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.32. simple_object_elf_match in simple-object-elf.c does not check for a zero shstrndx value, leading to an integer overflow and resultant heap-based buffer overflow.

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gcc48` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.8.5-31.26.1 |
| `gcc48` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.8.5-31.26.1 |
| `gcc48` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.8.5-31.26.1 |
| `libffi48` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.8.5-31.26.1 |
| `libgcj48` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.8.5-31.26.1 |
| `libgcj48` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 4.8.5-31.26.1 |

Products: Canonical Ubuntu Linux, Gnu Binutils, Opensuse Leap.

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

Apply the vendor's patch.

## Is CVE-2019-14250 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14250 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 24 Jul 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-14250 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-14250/ (Markdown: https://insights.sbomify.com/CVE-2019-14250/index.md)
```

## Sources

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

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