# CVE-2019-13655: Denial of service in n/a

> Remote attackers can cause denial of service in Imgix by sending a crafted JPEG file that triggers excessive memory consumption.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2797-489c-67fq

## What is CVE-2019-13655?

CVE-2019-13655 is a medium-severity denial of service vulnerability in n/a, published on 29 Jul 2019. 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

Imgix through 2019-06-19 allows remote attackers to cause a denial of service (resource consumption) by manipulating a small JPEG file to specify dimensions of 64250x64250 pixels, which is mishandled during an attempt to load the 'whole image' into memory.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2019-13655?

It affects 1 product.


Products: Imgix Imgix.

## How do I fix CVE-2019-13655?

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

## Is CVE-2019-13655 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13655 and fix it if it is affected.

What it is: CVE-2019-13655 is a medium-severity denial of service vulnerability in n/a, published on 29 Jul 2019. 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-2019-13655 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-2019-13655/ (Markdown: https://insights.sbomify.com/CVE-2019-13655/index.md)
```

## Sources

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

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