# OSV-2022-310: Heap-use-after-free in jpeg_fill_bit_buffer

> A heap-use-after-free vulnerability in the JPEG decoding library allows attackers to cause crashes or potentially execute code via malicious images.

- **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:** 6 Apr 2022

## What is OSV-2022-310?

OSV-2022-310 is an use after free vulnerability in libvips, published on 6 Apr 2022. 

### Official description

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

```
Crash type: Heap-use-after-free WRITE 4
Crash state:
jpeg_fill_bit_buffer
jpeg_huff_decode
decode_mcu
```

## Which versions are affected by OSV-2022-310?

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


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

## How do I fix OSV-2022-310?

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

## Is OSV-2022-310 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2022-310 and fix it if it is affected.

What it is: OSV-2022-310 is an use after free vulnerability in libvips, published on 6 Apr 2022. 
Exploitation: There is no known exploitation of OSV-2022-310 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2022-310

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