VideoLAN Says Flaws Exist in Codecs Library, Not VLC Itself

Two Vulnerabilities that Could Potentially be Exploited for Arbitrary Code Execution Exist in 'libavcodec', a Free and Open-Source Audio / Video Codecs Library Used by Several Popular Media Players. The Issues were Discovered Last Year by Turkey-Based Researcher, Veysel Hatas. Hatas Said, the Vulnerabilities Exist in the VLC Media Player and Even Got the MITRE Corporation to Assign them CVE Identifiers. However, VideoLAN, the Non-Profit Organization that Develops, VLC, Pointed Out that, the Security Holes actually Exist in 'libavcodec', which is Used as the Main Decoding Engine Not Only by VLC but, Several Other Media Players as well, including Xine and MPlayer. Jean-Baptiste Kempf, the President of VideoLAN and One of the Lead Developers of VLC, Believes that, Assigning the CVEs to VLC is “Just Wrong”.


“This is not a VLC security issue but, a libavcodec one”, Kempf Told SecurityWeek in an Email. “The researcher was told numerous times but, refused to acknowledge it.” In his Advisory, Hatas Said, the Security Holes Can be Exploited by a Context-Dependent Attacker to Corrupt Memory and Possibly Execute Arbitrary Code. The Researcher Says, the 1st Vulnerability is a DEP Access Violation Bug (CVE-2014-9597). “VLC Media Player contains a flaw that is triggered as user-supplied input is not properly sanitized when handling a specially crafted FLV file”, Reads the Advisory Published Last Week.


 In the Case of the 2nd Issue (CVE-2014-9598), which has been Described as a Write Access Violation Vulnerability by the Researcher, the Attack Involves Specially Crafted .M2V Files. Hatas Said, he Successfully Reproduced the Vulnerabilities on VLC 2.1.5, the Latest Stable Version of the Media Player, on Windows XP SP3. Kempf has Pointed Out that, VLC 2.1.5 on Linux is Not Affected because an Updated Version of the Library is Used. He has also Highlighted that, the Vulnerability Doesn’t Affect VLC 2.2.0-rc2 on any OS. Representatives of the FFmpeg Team, which Develops the 'libavcodec' Library, Told SecurityWeek that, they were Unable to Reproduce the Issues Reported by Hatas on VLC 2.1.5 Running on Windows 7. The Developers Have Tested Both the 32-Bit and 64-Bit Versions of VLC.




Info Source:

http://www.binarysniper.net/2015/01/vlc-media-player-215-memory-corruption.html