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

> Remote attackers can cause denial of service via crafted TIFF images due to improper handling of image dimensions in Netpbm.

- **Severity:** Medium 5.5 (`CVSS:3.0/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:** 15 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7c32-9pjx-pj89, SUSE-SU-2024:0434-1, SUSE-SU-2024:0435-1, openSUSE-SU-2024:13655-1

## What is CVE-2017-5849?

CVE-2017-5849 is a medium-severity memory corruption vulnerability in Fedoraproject Fedora, published on 15 Mar 2017. 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

tiffttopnm in netpbm 10.47.63 does not properly use the libtiff TIFFRGBAImageGet function, which allows remote attackers to cause a denial of service (out-of-bounds read and write) via a crafted tiff image file, related to transposing width and height values.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `netpbm` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 10.80.1-150000.3.14.1 |
| `netpbm` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 10.80.1-150000.3.14.1 |
| `netpbm` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 10.66.3-8.10.1 |
| `netpbm` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 10.66.3-8.10.1 |
| `netpbm` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 10.66.3-8.10.1 |
| `netpbm` | openSUSE:Leap 15.5 | All versions | 10.80.1-150000.3.14.1 |
| `netpbm` | openSUSE:Tumbleweed | All versions | 11.5.2-2.1 |

Products: Fedoraproject Fedora, Netpbm Project Netpbm.

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

Apply the vendor's patch.

## Is CVE-2017-5849 being exploited?

There is no known exploitation of CVE-2017-5849 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-2017-5849 and fix it if it is affected.

What it is: CVE-2017-5849 is a medium-severity memory corruption vulnerability in Fedoraproject Fedora, published on 15 Mar 2017. 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-2017-5849 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-2017-5849/ (Markdown: https://insights.sbomify.com/CVE-2017-5849/index.md)
```

## Sources

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

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