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

> Attackers can cause denial of service or potentially execute code via a crafted .rle file in XnView Classic for Windows.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6569-mwg4-jv4w

## What is CVE-2017-10769?

CVE-2017-10769 is a high-severity memory corruption vulnerability in Xnview Xnview, published on 5 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

XnView Classic for Windows Version 2.40 might allow attackers to cause a denial of service or possibly have unspecified other impact via a crafted .rle file, related to "Data from Faulting Address controls Branch Selection starting at ntdll_77df0000!memcmp+0x0000000000000018" (without RPC initialization).

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

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

It affects 1 product.


Products: Xnview Xnview.

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

No fix has been published for CVE-2017-10769 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-10769 being exploited?

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

## Other vulnerabilities in Xnview Xnview

- [CVE-2013-3492](https://insights.sbomify.com/CVE-2013-3492/): Memory corruption in XnView (critical 9.8)
- [CVE-2013-3493](https://insights.sbomify.com/CVE-2013-3493/): Integer overflow in XnView (critical 9.8)
- [CVE-2013-3941](https://insights.sbomify.com/CVE-2013-3941/): Memory corruption in XnView (critical 9.8)
- [CVE-2012-4988](https://insights.sbomify.com/CVE-2012-4988/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3938](https://insights.sbomify.com/CVE-2013-3938/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10769 is a high-severity memory corruption vulnerability in Xnview Xnview, published on 5 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10769 in the wild and no public exploit code.

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

## Sources

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

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