# GHSA-jh2j-j4j9-crg3: opencv-python-headless bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863

> Attackers can execute arbitrary code or cause denial of service by tricking users into processing malicious WebP images with vulnerable opencv-python-headless versions.

- **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:** 30 Aug 2024

## What is GHSA-jh2j-j4j9-crg3?

GHSA-jh2j-j4j9-crg3 is a memory corruption vulnerability in opencv-python-headless, published on 30 Aug 2024. 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

opencv-python-headless versions before v4.8.1.78 bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863. opencv-python-headless v4.8.1.78 upgrades the bundled libwebp binary to v1.3.2.

## Which versions are affected by GHSA-jh2j-j4j9-crg3?

2 open source packages ship an affected version, including opencv-python-headless.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `opencv-python-headless` | PyPI | All versions | 4.8.1.78 |
| `opencv-python-headless` | PyPI | All versions | 4.8.1.78 |

## How do I fix GHSA-jh2j-j4j9-crg3?

Upgrade opencv-python-headless to 4.8.1.78 or later.

## Is GHSA-jh2j-j4j9-crg3 being exploited?

There is no known exploitation of GHSA-jh2j-j4j9-crg3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-jh2j-j4j9-crg3 and fix it if it is affected.

What it is: GHSA-jh2j-j4j9-crg3 is a memory corruption vulnerability in opencv-python-headless, published on 30 Aug 2024. 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-jh2j-j4j9-crg3 in the wild and no public exploit code.

Affected packages and fixed versions:
- opencv-python-headless (PyPI): affected all versions; fixed in 4.8.1.78
- opencv-python-headless (PyPI): affected all versions; fixed in 4.8.1.78

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-jh2j-j4j9-crg3/ (Markdown: https://insights.sbomify.com/GHSA-jh2j-j4j9-crg3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-jh2j-j4j9-crg3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-jh2j-j4j9-crg3/
Summaries are generated and may contain mistakes; the official description above is the record.