# OSV-2020-197: Heap-buffer-overflow in jbig2_image_get_pixels_fast

> A heap-buffer-overflow in the JBIG2 image decoder allows attackers to cause denial of service or potentially execute code via crafted images.

- **Severity:** Not scored
- **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:** 24 Jun 2020

## What is OSV-2020-197?

OSV-2020-197 is a memory corruption vulnerability in jbig2dec, published on 24 Jun 2020. 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

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

```
Crash type: Heap-buffer-overflow READ 1
Crash state:
jbig2_image_get_pixels_fast
jbig2_decode_generic_template0_TPGDON
jbig2_immediate_generic_region
```

## Which versions are affected by OSV-2020-197?

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


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

## How do I fix OSV-2020-197?

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

## Is OSV-2020-197 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-197 and fix it if it is affected.

What it is: OSV-2020-197 is a memory corruption vulnerability in jbig2dec, published on 24 Jun 2020. 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 OSV-2020-197 in the wild and no public exploit code.

Affected packages and fixed versions:
- jbig2dec (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-2020-197/ (Markdown: https://insights.sbomify.com/OSV-2020-197/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-197

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