OSV-2022-394 Incorrect-function-pointer-type in cv::split
Not scored
Published
Check this codebase for OSV-2022-394 and fix it if it is affected.
What it is: OSV-2022-394 is a vulnerability in opencv, published on 4 May 2022.
Exploitation: There is no known exploitation of OSV-2022-394 in the wild and no public exploit code.
Affected packages and fixed versions:
- opencv (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-394/ (Markdown: https://insights.sbomify.com/OSV-2022-394/index.md)
A crash in OpenCV's cv::split function due to an incorrect function pointer type can cause denial of service when processing images.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2022-394?
OSV-2022-394 is a vulnerability in opencv, published on 4 May 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47190
Crash type: Incorrect-function-pointer-type
Crash state:
cv::split
cv::split
TestSplitAndMerge
Which versions are affected by OSV-2022-394?
1 open source package ship an affected version, including opencv.
| Package | Affected | Fixed in |
|---|---|---|
opencv OSS-Fuzz | All versions | None |
How do I fix OSV-2022-394?
No fix has been published for OSV-2022-394 yet. Limit exposure of the affected software until one is available.
Is OSV-2022-394 being exploited?
There is no known exploitation of OSV-2022-394 in the wild and no public exploit code.