# CVE-2024-44083: Denial of service in n/a

> A crafted binary with many linked jumps causes IDA Pro to crash, resulting in a denial of service for users analyzing the file.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2024
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-q632-7v8j-586g

## What is CVE-2024-44083?

CVE-2024-44083 is a high-severity denial of service vulnerability in n/a, published on 19 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ida64.dll in Hex-Rays IDA Pro through 8.4 crashes when there is a section that has many jumps linked, and the final jump corresponds to the payload from where the actual entry point will be invoked. NOTE: in many use cases, this is an inconvenience but not a security issue.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Hex-Rays Ida Pro.

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

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

## Is CVE-2024-44083 being exploited?

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

Public exploit code:

- Makes IDA (all versions) to crash upon opening it.  (github_poc): https://github.com/CrackerCat/CVE-2024-44083
- my CVE-2024-44083 poc. (github_poc): https://github.com/dynamicx64/CVE-2024-44083

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44083 is a high-severity denial of service vulnerability in n/a, published on 19 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44083 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-44083/ (Markdown: https://insights.sbomify.com/CVE-2024-44083/index.md)
```

## Sources

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

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