# CVE-2005-1544: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malicious TIFF file with a malformed BitsPerSample tag.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 14 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-1544, DSA-755-1, GHSA-45px-6f9w-fmpf

## What is CVE-2005-1544?

CVE-2005-1544 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 14 May 2005. 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

Stack-based buffer overflow in libTIFF before 3.7.2 allows remote attackers to execute arbitrary code via a TIFF file with a malformed BitsPerSample tag.

## Which versions are affected by CVE-2005-1544?

It affects 1 product.


Products: Libtiff Libtiff.

## How do I fix CVE-2005-1544?

Upgrade to a fixed version.

## Is CVE-2005-1544 being exploited?

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

Public exploit code:

- LibTiff 3.7.1 - BitsPerSample Tag Local Buffer Overflow (exploitdb)

## Other vulnerabilities in Libtiff Libtiff

- [CVE-2004-1308](https://insights.sbomify.com/CVE-2004-1308/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0929](https://insights.sbomify.com/CVE-2004-0929/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-61144](https://insights.sbomify.com/CVE-2025-61144/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9533](https://insights.sbomify.com/CVE-2016-9533/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9534](https://insights.sbomify.com/CVE-2016-9534/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1544 and fix it if it is affected.

What it is: CVE-2005-1544 is a high-severity memory corruption vulnerability in Libtiff Libtiff, published on 14 May 2005. An attacker can exploit it over the internet without logging in, 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-2005-1544 exists.

Affected product: Libtiff Libtiff. 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-2005-1544/ (Markdown: https://insights.sbomify.com/CVE-2005-1544/index.md)
```

## Sources

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

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