# CVE-2017-14226: Memory corruption in n/a

> Remote attackers can cause a denial of service via heap-based buffer over-read in libwpd, affecting LibreOffice users.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2017
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-14226, GHSA-4m96-cjx2-px9q, MGASA-2017-0358, SUSE-SU-2017:2931-1, UBUNTU-CVE-2017-14226

## What is CVE-2017-14226?

CVE-2017-14226 is a high-severity memory corruption vulnerability in Libreoffice Libreoffice, published on 9 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WP1StylesListener.cpp, WP5StylesListener.cpp, and WP42StylesListener.cpp in libwpd 0.10.1 mishandle iterators, which allows remote attackers to cause a denial of service (heap-based buffer over-read in the WPXTableList class in WPXTable.cpp). This vulnerability can be triggered in LibreOffice before 5.3.7. It may lead to suffering a remote attack against a LibreOffice application.

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

## Which versions are affected by CVE-2017-14226?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libwpd` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 0.10.2-2.4.1 |
| `libwpd` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 0.10.2-2.4.1 |
| `libwpd` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 0.10.2-2.4.1 |
| `libwpd` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 0.10.2-2.4.1 |
| `libwpd` | SUSE:Linux Enterprise Workstation Extension 12 SP2 | All versions | 0.10.2-2.4.1 |
| `libwpd` | SUSE:Linux Enterprise Workstation Extension 12 SP3 | All versions | 0.10.2-2.4.1 |

Products: Libreoffice Libreoffice, Libwpd Libwpd.

## How do I fix CVE-2017-14226?

Upgrade to a fixed version.

## Is CVE-2017-14226 being exploited?

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

## Other vulnerabilities in Libreoffice Libreoffice

- [CVE-2024-5261](https://insights.sbomify.com/CVE-2024-5261/): TLS certificate are not properly verified when utilizing LibreOfficeKit (critical 10.0)
- [CVE-2019-9855](https://insights.sbomify.com/CVE-2019-9855/): Windows 8.3 path equivalence handling flaw allows LibreLogo script execution (critical 9.8)
- [CVE-2018-14939](https://insights.sbomify.com/CVE-2018-14939/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8358](https://insights.sbomify.com/CVE-2017-8358/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7882](https://insights.sbomify.com/CVE-2017-7882/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14226 and fix it if it is affected.

What it is: CVE-2017-14226 is a high-severity memory corruption vulnerability in Libreoffice Libreoffice, published on 9 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14226 in the wild and no public exploit code.

Affected product: Libreoffice Libreoffice. 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-2017-14226/ (Markdown: https://insights.sbomify.com/CVE-2017-14226/index.md)
```

## Sources

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

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