MPlayer, VLC Media Player Hit By Critical Vulnerability (hackread.com)
A critical remote code execution vulnerability has been spotted in the LIVE555 media streaming library used by popular media players such as VLC and MPlayer. "Maintained by the company Live Networks, the library works with RTP / RTCP, RTSP or SIP protocols, with the ability to process video and audio formats such as MPEG, H.265, H.264, H.263 +, VP8, DV, JPEG, MPEG, AAC, AMR, AC-3, and Vorbis," reports Hackread. From the report: These findings (CVE-2018-4013) have left millions of users of media players vulnerable to cyber attacks, according to Lilith Wyatt, a researcher at the Cisco Talos Intelligence Group. In this case, the flaw lies in the HTTP packet parsing functionality, which analyzes HTTP headers for RTSP tunneling over HTTP, explains. An update has already been issued to address the vulnerability. Therefore, if you are using any of the vulnerable media players make sure they are updated to the latest version.
It's still 3.0.4 which I've had for a while now.
It would be helpful if articles such as this listed what VLC versions (or other software) have addressed this flaw, rather than just say have the latest updated. From the article the assumption is if you have the Win/OS X/Linux updated to the latest version you are not vulnerable.
I'm a consultant - I convert gibberish into cash-flow.
Last time I tried it, the control interface couldn't be moved to another monitor. Plus, it could only use a limited number of video output modules, some of which were blocky or poor performing.
Almost nobody that uses VLC will actually be affected by this bug
Debian users, do this right away:
sudo apt upgrade && sudo apt install liblivemedia62:amd64 liblivemedia64:amd64
For buster/sid, this updates to versions 2018.10.17-1 and 2018.08.28a-1. Then check to see if these have the fix, I think they do but I have not verified yet.
This update takes less than 1 minute to do, there is not the slightest excuse for procrastinating.
When all you have is a hammer, every problem starts to look like a thumb.
As of 2018-10-21 01:35 EDT three is no update for VLC Media Player they are still at 3.0.4 from a month or two back. Version 3.0.5 would be the updated version.
The bug - which has now been fixed in the LIVE555 library (with the fix already reported to Cisco) - affected only the LIVE555 library's implementation of a RTSP *server*. It doesn't affect the implementation of a RTSP *client*, which is the only part of the LIVE555 library that VLC and MPlayer use. (VLC does have an embedded RTSP server, but that uses a separate implementation, not LIVE555's.)
(I know this because I'm the author of the LIVE555 software :-)
Would any existing static checker free for use with open source have identified the bug?
If yes, then there should be an obligation to use them in key software.
If no, then we need to sort out the lack of testing common in the software industry as a whole.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
if using the application only to watch offline videos affected?
Never 'apt upgrade' or perform any other apt operation without first running 'apt update' to make sure that you are working with the latest package sets.
People who complain about practically nonexistent problems such as "dependency hell" are always painting themselves into this corner...
This article is grossly inaccurate and blatantly wrong. https://twitter.com/videolan/s... + https://twitter.com/hanno/stat...
"
Update:
According to an email from Ross Finlayson of Live Networks, Inc., the vulnerability “does not affect VLC or MPlayer, because they use LIVE555 only to implement an RTSP. The bug affected only our implementation of a RTSP, which these media players don’t use. (VLC does have an embedded RTSP server, but that uses a separate implementation, not LIVE555’s.)”
"
Please can the slashdot editors fix the headline and summary to reflect the actual situation as per Ross Finlayson's post. Which is to say Mplayer and VLC Media Player were not vulnerable and there's no need to panic. The article linked to in the summary is plain wrong and really needs to be retracted.
According to an email from Ross Finlayson of Live Networks, Inc., the vulnerability “does not affect VLC or MPlayer, because they use LIVE555 only to implement an RTSP. The bug affected only our implementation of a RTSP, which these media players don’t use. (VLC does have an embedded RTSP server, but that uses a separate implementation, not LIVE555’s.)”