# CVE-2023-36308: Crash when processing crafted TIFF files

> A crafted TIFF file triggers an integer index out of range panic in the disintegration Imaging library, causing a denial of service.

- **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:** 5 Sep 2023
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-36308, GHSA-q7pp-wcgr-pffx

## What is CVE-2023-36308?

CVE-2023-36308 is a medium-severity vulnerability in n/a, published on 5 Sep 2023. 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

disintegration Imaging 1.6.2 allows attackers to cause a panic (because of an integer index out of range during a Grayscale call) via a crafted TIFF file to the scan function of scanner.go. NOTE: it is unclear whether there are common use cases in which this panic could have any security consequence

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2023-36308?

2 open source packages ship an affected version, including github.com/disintegration/imaging. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/disintegration/imaging` | Go | All versions to 1.6.2 | None |
| `github.com/disintegration/imaging` | Go | All versions to 1.6.2 | None |

Products: Disintegration Imaging.

## How do I fix CVE-2023-36308?

Upgrade to a fixed version.

## Is CVE-2023-36308 being exploited?

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

Public exploit code:

- Security-maintenance fork of disintegration/imaging (CVE-2023-36308 fix) used by Tala WTE (github_poc): https://github.com/vtemlabs/imaging

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36308 and fix it if it is affected.

What it is: CVE-2023-36308 is a medium-severity vulnerability in n/a, published on 5 Sep 2023. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36308 exists.

Affected packages and fixed versions:
- github.com/disintegration/imaging (Go): affected all versions up to 1.6.2; no fix listed
- github.com/disintegration/imaging (Go): affected all versions up to 1.6.2; no fix listed

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-2023-36308/ (Markdown: https://insights.sbomify.com/CVE-2023-36308/index.md)
```

## Sources

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

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