Heap Buffer Overflow Vulnerability in libavc: Critical Security Flaw
Summary
OSV-2025-584: Heap-buffer-overflow in isvcd_mark_err_slice_skip. Affects libavc versions >= 2f6371b3b8d69ee596fa44c48ca522db27f6f22f, < b34ac3d492b0a46691a5949c19f30fd844c37396. Fixed in b34ac3d492b0a46691a5949c19f30fd844c37396. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
libavc is an open-source video codec library developed by Ittiam Systems, designed for efficient video encoding and decoding. It is widely used in various multimedia applications due to its performance and support for multiple video formats. However, like many software libraries, it is susceptible to vulnerabilities that can compromise the security and stability of applications that utilize it.
Vulnerability Detail
The vulnerability identified as OSV-2025-584 is a heap buffer overflow that occurs in the function isvcd_mark_err_slice_skip within the libavc library. This flaw can lead to potential crashes or arbitrary code execution, allowing attackers to exploit the affected application. The issue arises from improper handling of memory allocation, leading to a situation where the application reads beyond the allocated buffer, resulting in a heap buffer overflow. This vulnerability was reported through OSS-Fuzz, highlighting its critical nature and the need for immediate attention.
How To Fix
Minimum fixed version
b34ac3d492b0a46691a5949c19f30fd844c37396
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, users can avoid using the specific functionality that triggers the vulnerability, namely the isvcd_mark_err_slice_skip function, until the library is updated. This may involve modifying the application code to bypass error handling related to slice skipping.
Conclusion
The heap buffer overflow vulnerability in the libavc library poses a significant risk to applications that utilize this codec. Immediate action is required to update to the patched version to mitigate potential security threats. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert to ensure ongoing security.
See every vulnerability recorded for libavc →
FAQ
A heap buffer overflow occurs when a program writes more data to a buffer located on the heap than it was allocated for, potentially leading to data corruption, crashes, or security vulnerabilities.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By simply uploading your manifest file like package-lock.json, you can check for vulnerabilities without needing to access the code.
Exploitation of this vulnerability can lead to application crashes, unauthorized access, or execution of arbitrary code, which can compromise the security of the system.
While the best solution is to update to the patched version, you can temporarily avoid using the affected function until the update is applied.
Detailed information can be found in the OSS-Fuzz report at https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=434978682.
References
Related vulnerabilities
Recent vulnerabilities recorded for libavc.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
