FFmpeg Multiple Security Vulnerabilities
BID:65671
Info
FFmpeg Multiple Security Vulnerabilities
| Bugtraq ID: | 65671 |
| Class: | Boundary Condition Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Feb 18 2014 12:00AM |
| Updated: | Mar 11 2014 01:03AM |
| Credit: | Mateusz "j00ru" Jurczyk and Gynvael Coldwind |
| Vulnerable: | |
| Not Vulnerable: | |
Discussion
FFmpeg Multiple Security Vulnerabilities
FFmpeg is prone to multiple remote security vulnerabilities.
An attacker can exploit these issues to execute arbitrary code in the context of the user running the affected application. Failed exploit attempts will likely result in denial-of-service conditions.
NOTE: Issues related to out-of-bound error have been moved to BID 66060 (FFmpeg and Libav 'msrle_decode_frame()' Function Out of Bounds Denial of Service Vulnerability) to better document them.
FFmpeg is prone to multiple remote security vulnerabilities.
An attacker can exploit these issues to execute arbitrary code in the context of the user running the affected application. Failed exploit attempts will likely result in denial-of-service conditions.
NOTE: Issues related to out-of-bound error have been moved to BID 66060 (FFmpeg and Libav 'msrle_decode_frame()' Function Out of Bounds Denial of Service Vulnerability) to better document them.
Exploit / POC
FFmpeg Multiple Security Vulnerabilities
Currently, we are not aware of any working exploits. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Currently, we are not aware of any working exploits. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution / Fix
FFmpeg Multiple Security Vulnerabilities
Solution:
Currently, we are not aware of any vendor-supplied patches. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].
Solution:
Currently, we are not aware of any vendor-supplied patches. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].