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

> A heap-based buffer overflow in the Perl Imager library allows attackers to cause denial of service via crafted images.

- **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:** Yes
- **Published:** 24 Nov 2024
- **Updated:** 24 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-53901, GHSA-cwgj-pq49-6x66, UBUNTU-CVE-2024-53901

## What is CVE-2024-53901?

CVE-2024-53901 is a medium-severity memory corruption vulnerability in n/a, published on 24 Nov 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

The Imager package before 1.025 for Perl has a heap-based buffer overflow leading to denial of service, or possibly unspecified other impact, when the trim() method is called on a crafted input image.

Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Tonycoz Imager.

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

Upgrade to a fixed version.

## Is CVE-2024-53901 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-14454](https://insights.sbomify.com/CVE-2026-14454/): Imager versions before 1.033 for Perl treat unsigned EXIF IFD entry counts as signed (critical 9.8)
- [CVE-2026-102504](https://insights.sbomify.com/CVE-2026-102504/): Denial of service in tonycoz:imager (high 7.5)
- [CVE-2026-102505](https://insights.sbomify.com/CVE-2026-102505/): Memory corruption in tonycoz:imager (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53901 is a medium-severity memory corruption vulnerability in n/a, published on 24 Nov 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: There is no known exploitation of CVE-2024-53901 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-53901/ (Markdown: https://insights.sbomify.com/CVE-2024-53901/index.md)
```

## Sources

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

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