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

> Attackers can cause a denial of service via a crafted image file due to an assertion failure in the Jasper library.

- **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:** Yes
- **Published:** 19 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-40000, GHSA-4pvq-mcwh-v9jc, MGASA-2024-0144, SUSE-SU-2024:1396-1, SUSE-SU-2024:1464-1, UBUNTU-CVE-2024-31744, openSUSE-SU-2024:13878-1

## What is CVE-2024-31744?

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

### Official description

In Jasper 4.2.2, the jpc_streamlist_remove function in src/libjasper/jpc/jpc_dec.c:2407 has an assertion failure vulnerability, allowing attackers to cause a denial of service attack through a specific image file.

Weakness: CWE-617 (Reachable Assertion)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jasper` | SUSE:Enterprise Storage 7.1 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.900.14-195.40.1 |
| `jasper` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.900.14-195.40.1 |
| `jasper` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.900.14-195.40.1 |
| `jasper` | SUSE:Manager Proxy 4.3 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | SUSE:Manager Server 4.3 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | openSUSE:Leap 15.5 | All versions | 2.0.14-150000.3.34.1 |
| `jasper` | openSUSE:Tumbleweed | All versions | 4.2.3-2.1 |

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

Apply the vendor's patch.

## Is CVE-2024-31744 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31744 is a high-severity denial of service vulnerability in n/a, published on 19 Apr 2024. 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-2024-31744 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-2024-31744/ (Markdown: https://insights.sbomify.com/CVE-2024-31744/index.md)
```

## Sources

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

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