# CVE-2024-31007: Memory corruption in n/a

> A local attacker can cause a denial of service in IrfanView by opening a crafted file, exploiting a buffer overflow in the formats.dll plugin.

- **Severity:** Medium 5.5 (`CVSS:3.1/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:** No
- **Published:** 21 Oct 2024
- **Updated:** 21 Oct 2024
- **Also known as:** GHSA-j9rm-v8cj-vm2c

## What is CVE-2024-31007?

CVE-2024-31007 is a medium-severity memory corruption vulnerability in n/a, published on 21 Oct 2024. 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

Buffer Overflow vulnerability in IrfanView 32bit v.4.66 allows a local attacker to cause a denial of service via a crafted file. Affected component is IrfanView 32bit 4.66 with plugin formats.dll.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-31007?


## How do I fix CVE-2024-31007?

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

## Is CVE-2024-31007 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31007 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31007 and fix it if it is affected.

What it is: CVE-2024-31007 is a medium-severity memory corruption vulnerability in n/a, published on 21 Oct 2024. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31007 exists.

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-2024-31007/ (Markdown: https://insights.sbomify.com/CVE-2024-31007/index.md)
```

## Sources

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

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