[Solved] VLC 3.0.3 detected as safe
-
FYI:
https://www.videolan.org/security/ "... Please note: The VideoLAN project does not issue security advisories for underlying third party libraries. Please refer to the concerned third parties as appropriate. ..."BTW, there is a secuirty issue in LIVE555 media streaming library, but this should not influence vlc, see:
https://www.hackread.com/watch-out-for-this-vulnerability-in-vlc-mplayer/ (October 20th, 2018)
https://talosintelligence.com/vulnerability_reports/TALOS-2018-0684
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4013 -
@Anselm Thank you
-
This post is deleted! -
Hi Tom,
When I launched VLC I got a message that a new version was available and fixing security issues. I patched, reported and did not look for anything else: as you pinpointed they are quite good for security and providing information.
I remember that I was a bit surprised to have miss this in security bulletins that I receive: it seems that I was not so bad.
I am not alone with this: https://portableapps.com/news/2018-09-01--vlc-media-player-portable-3.0.4-released
I also found that (https://www.wilderssecurity.com/threads/vlc-3-0-vetinari-released.400558/page-3
"The changelog for 3.0.4 doesn't mention security fixes specifically, but the release notes in the built-in updater do:
VideoLAN and the VLC development team present VLC 3.0 "Vetinari".
VLC 3.0.4 is a minor update to VLC 3.0 branch, fixes numerous hardware decoding issues, adds support for AV1 streams and fixes security issues. It also improves the support for numerous formats, and regressions in video quality compared to 2.2.x, in certain cases.""I am quite sure that I read this somewhere as I was surprised they let regressions and that I had (have) no idea of what is an "AV1 stream".
Hope this helps.
Regards.
Greg. -
Maybe a copy paste error?
https://portableapps.com/news/2018-09-01--vlc-media-player-portable-3.0.4-released (This version fixes a critical security issue in VLC.)
https://portableapps.com/news/2018-05-31--vlc-media-player-portable-3.0.3-released ( This version fixes a critical security issue in VLC.)
https://portableapps.com/news/2018-05-06--vlc-media-player-portable-3.0.2-released (This version fixes a critical security issue in VLC. )
https://portableapps.com/news/2018-03-21--vlc-media-player-portable-3.0.1-released (This version fixes a critical security issue in VLC.) -
Unless some more tangible report comes out, then we will keep flagging 3.0.2, 3.0.3 and 3.0.4 as "OK", with 3.0.4 being the recommended version.
But thank you for reporting this, in this time and age you can't just rely on vendors to report all issues, so when you see reports elsewhere, then please post here or send me a chat message and we will investigate.
-
-
Thank you.
Yeah, well, as we discussed that, it seems that a guy has found a vuln in 3.0.4.
So it is time to flag all versions as being "Insecure"
Let's hope a new release of VLC comes out one of the next days.
CVE Details is a great site for getting some high level information about the history of a product.
However, CVE itself, has seen better days, unfortunately a lot of vulns are assigned CVEs rather late and a lot never receives a CVE.
Just look at yesterdays Chrome release, where some of the vulns are "To be allocated [a CVE]". That seems odd for such a significant app as Chrome:
https://chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html -
Tom, is the issue solved (after you flagged all versions as being "Insecure")?
-
@Tom says, 3.0.2, 3.0.3, 3.0.4 are not insecure, but 3.0.4 is recommended . I only found an information, that 3.0.1 is insecure.
-
-
@Tom OK, i did not see it at cve.mitre.org using the search.
-
@Anselm Correction: OK, i did not see it yesterday at cve.mitre.org using the search. But now i knew why:
Date Entry Created
20181205 -
@Anselm VLC 3.0.5 is out
-
@Tom Thank you, I updated it yesterday
-
@Tom
From changelog 3.0.4 to 3.0.5
"Update numerous 3rd party libraries, including for minor security issues"This subject could be close.
Thanks a lot Tom.
-
@GregAlexandre OK, then I mark the topic as Solved
