OSV-2021-600 Heap-buffer-overflow in gif_internal_decode_frame
Not scored
Published
Check this codebase for OSV-2021-600 and fix it if it is affected.
What it is: OSV-2021-600 is a memory corruption vulnerability in libvips, published on 4 Apr 2021.
Exploitation: There is no known exploitation of OSV-2021-600 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-2021-600/ (Markdown: https://insights.sbomify.com/OSV-2021-600/index.md)
A heap-buffer-overflow in the GIF decoder allows attackers to cause crashes or potentially execute code via malicious image files.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2021-600?
OSV-2021-600 is a memory corruption vulnerability in libvips, published on 4 Apr 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32855
Crash type: Heap-buffer-overflow WRITE {*}
Crash state:
gif_internal_decode_frame
gif_decode_frame
vips_foreign_load_nsgif_generate
Which versions are affected by OSV-2021-600?
1 open source package ship an affected version, including libvips.
| Package | Affected | Fixed in |
|---|---|---|
libvips OSS-Fuzz | All versions | None |
How do I fix OSV-2021-600?
No fix has been published for OSV-2021-600 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2021-600 being exploited?
There is no known exploitation of OSV-2021-600 in the wild and no public exploit code.