# GHSA-4vjr-crvh-383h: @napi-rs/image affected by libwebp CVE

> A heap buffer overflow in libwebp allows remote attackers to execute arbitrary code via a crafted WebP image processed by the @napi-rs/image library.

- **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:** Yes
- **Published:** 27 Sep 2023

## What is GHSA-4vjr-crvh-383h?

GHSA-4vjr-crvh-383h is a memory corruption vulnerability in @napi-rs/image, published on 27 Sep 2023. 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

### Impact
Heap buffer overflow in `libwebp` allows a remote attacker to perform an out of bounds memory write via a crafted webp image.

### References
- https://github.com/advisories/GHSA-j7hp-h8jx-5ppr
- https://blog.isosceles.com/the-webp-0day/

## Which versions are affected by GHSA-4vjr-crvh-383h?

2 open source packages ship an affected version, including @napi-rs/image.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@napi-rs/image` | npm | All versions | 1.7.0 |
| `@napi-rs/image` | npm | All versions | 1.7.0 |

## How do I fix GHSA-4vjr-crvh-383h?

Upgrade @napi-rs/image to 1.7.0 or later.

## Is GHSA-4vjr-crvh-383h being exploited?

There is no known exploitation of GHSA-4vjr-crvh-383h in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4vjr-crvh-383h and fix it if it is affected.

What it is: GHSA-4vjr-crvh-383h is a memory corruption vulnerability in @napi-rs/image, published on 27 Sep 2023. 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 GHSA-4vjr-crvh-383h in the wild and no public exploit code.

Affected packages and fixed versions:
- @napi-rs/image (npm): affected all versions; fixed in 1.7.0
- @napi-rs/image (npm): affected all versions; fixed in 1.7.0

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/GHSA-4vjr-crvh-383h/ (Markdown: https://insights.sbomify.com/GHSA-4vjr-crvh-383h/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4vjr-crvh-383h

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4vjr-crvh-383h/
Summaries are generated and may contain mistakes; the official description above is the record.