# CVE-2017-2813: Integer overflow in Irfanview

> A specially crafted JPEG 2000 image can trigger an integer overflow in IrfanView, leading to arbitrary code execution when the image is viewed or thumbnailed.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jfp8-qmrf-q9h4

## What is CVE-2017-2813?

CVE-2017-2813 is a high-severity vulnerability in Irfanview Irfanview, published on 21 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An exploitable integer overflow vulnerability exists in the JPEG 2000 parser functionality of IrfanView 4.44. A specially crafted jpeg2000 image can cause an integer overflow leading to wrong memory allocation resulting in arbitrary code execution. Vulnerability can be triggered by viewing the image in via the application or by using thumbnailing feature of IrfanView.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Irfanview Irfanview.

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

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

## Is CVE-2017-2813 being exploited?

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

## Other vulnerabilities in Irfanview Irfanview

- [CVE-2007-1867](https://insights.sbomify.com/CVE-2007-1867/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0493](https://insights.sbomify.com/CVE-2008-0493/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-1948](https://insights.sbomify.com/CVE-2007-1948/): Memory corruption in n/a (critical 9.3)
- [CVE-2020-13905](https://insights.sbomify.com/CVE-2020-13905/): Memory corruption in n/a (high 8.8)
- [CVE-2007-2363](https://insights.sbomify.com/CVE-2007-2363/): Memory corruption in n/a (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2813 is a high-severity vulnerability in Irfanview Irfanview, published on 21 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-2813 in the wild and no public exploit code.

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

## Sources

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

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