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

> An attacker can trigger memory corruption in sam2p via a crafted XPM file, potentially leading to code execution or application crash.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 22 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rjmx-944x-fp54, UBUNTU-CVE-2017-14637

## What is CVE-2017-14637?

CVE-2017-14637 is a critical memory corruption vulnerability in n/a, published on 22 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In sam2p 0.49.3, there is an invalid read of size 2 in the parse_rgb function in in_xpm.cpp. However, this can also cause a write to an illegal address.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Sam2p Project Sam2p.

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

Upgrade to a fixed version.

## Is CVE-2017-14637 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12578](https://insights.sbomify.com/CVE-2018-12578/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-14636](https://insights.sbomify.com/CVE-2017-14636/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-14628](https://insights.sbomify.com/CVE-2017-14628/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-14630](https://insights.sbomify.com/CVE-2017-14630/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-14631](https://insights.sbomify.com/CVE-2017-14631/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14637 is a critical memory corruption vulnerability in n/a, published on 22 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-14637 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-2017-14637/ (Markdown: https://insights.sbomify.com/CVE-2017-14637/index.md)
```

## Sources

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

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