# GHSA-f9pm-4g9p-6vm3: Bundled libwebp in pywebp vulnerable

> A heap buffer overflow in the bundled libwebp allows remote attackers to execute arbitrary code via malicious WebP 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:** Yes
- **Published:** 6 Oct 2023

## What is GHSA-f9pm-4g9p-6vm3?

GHSA-f9pm-4g9p-6vm3 is a memory corruption vulnerability in webp, published on 6 Oct 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
pywebp versions before v0.3.0 bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863. The vulnerability was a heap buffer overflow which allowed a remote attacker to perform an out of bounds memory write.

### Patches
The problem has been patched upstream in libwebp 1.3.2.
pywebp was updated to bundle a patched version of libwebp in v0.3.0.

### Workarounds
No known workarounds without upgrading.

### References
- https://www.rezilion.com/blog/rezilion-researchers-uncover-new-details-on-severity-of-google-chrome-zero-day-vulnerability-cve-2023-4863/
- https://nvd.nist.gov/vuln/detail/CVE-2023-4863

## Which versions are affected by GHSA-f9pm-4g9p-6vm3?

2 open source packages ship an affected version, including webp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `webp` | PyPI | All versions | 0.3.0 |
| `webp` | PyPI | All versions | 0.3.0 |

## How do I fix GHSA-f9pm-4g9p-6vm3?

Upgrade webp to 0.3.0 or later.

## Is GHSA-f9pm-4g9p-6vm3 being exploited?

There is no known exploitation of GHSA-f9pm-4g9p-6vm3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f9pm-4g9p-6vm3 and fix it if it is affected.

What it is: GHSA-f9pm-4g9p-6vm3 is a memory corruption vulnerability in webp, published on 6 Oct 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-f9pm-4g9p-6vm3 in the wild and no public exploit code.

Affected packages and fixed versions:
- webp (PyPI): affected all versions; fixed in 0.3.0
- webp (PyPI): affected all versions; fixed in 0.3.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-f9pm-4g9p-6vm3/ (Markdown: https://insights.sbomify.com/GHSA-f9pm-4g9p-6vm3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f9pm-4g9p-6vm3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f9pm-4g9p-6vm3/
Summaries are generated and may contain mistakes; the official description above is the record.