OSV-2023-1305 Check failed in CheckUnwind
Not scored
Published
Check this codebase for OSV-2023-1305 and fix it if it is affected.
What it is: OSV-2023-1305 is a denial of service vulnerability in libavc, published on 15 Dec 2023.
Exploitation: There is no known exploitation of OSV-2023-1305 in the wild and no public exploit code.
Affected packages and fixed versions:
- libavc (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-2023-1305/ (Markdown: https://insights.sbomify.com/OSV-2023-1305/index.md)
A check failure in the H.264 decoder's unwind logic can cause a crash, leading to denial of service for applications using the library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2023-1305?
OSV-2023-1305 is a denial of service vulnerability in libavc, published on 15 Dec 2023.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65035
Crash type: Check failed
Crash state:
CheckUnwind
iv_aligned_free
ih264d_free_dynamic_bufs
Which versions are affected by OSV-2023-1305?
1 open source package ship an affected version, including libavc.
| Package | Affected | Fixed in |
|---|---|---|
libavc OSS-Fuzz | All versions | None |
How do I fix OSV-2023-1305?
No fix has been published for OSV-2023-1305 yet. Limit exposure of the affected software until one is available.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is OSV-2023-1305 being exploited?
There is no known exploitation of OSV-2023-1305 in the wild and no public exploit code.