# OSV-2017-35: Heap-buffer-overflow in opj_dwt_decode_partial_tile

> A heap-buffer-overflow in OpenJPEG allows attackers to cause denial of service or potentially execute code via crafted image files.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2021

## What is OSV-2017-35?

OSV-2017-35 is a memory corruption vulnerability in openjpeg, published on 13 Jan 2021. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3125

```
Crash type: Heap-buffer-overflow READ {*}
Crash state:
opj_dwt_decode_partial_tile
opj_tcd_dwt_decode
opj_tcd_decode_tile
```

## Which versions are affected by OSV-2017-35?

1 open source package ship an affected version, including openjpeg.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openjpeg` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2017-35?

No fix has been published for OSV-2017-35 yet. Limit exposure of the affected software until one is available.

## Is OSV-2017-35 being exploited?

There is no known exploitation of OSV-2017-35 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2017-35 and fix it if it is affected.

What it is: OSV-2017-35 is a memory corruption vulnerability in openjpeg, published on 13 Jan 2021. 
Exploitation: There is no known exploitation of OSV-2017-35 in the wild and no public exploit code.

Affected packages and fixed versions:
- openjpeg (OSS-Fuzz): affected all versions; 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/OSV-2017-35/ (Markdown: https://insights.sbomify.com/OSV-2017-35/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2017-35

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