MP3 Backend of Firefox and Thunderbird Found Vulnerable
jones_supa writes A critical vulnerability has been found in the MPEG-1 Layer III playback backend of Mozilla Firefox and Thunderbird. Security researcher Aki Helin reported a use-after-free scenario when playing certain audio files on the web using the Fluendo MP3 plugin for GStreamer on Linux. This is due to a flaw in handling certain MP3 files by the plugin and its interaction with Mozilla code. A maliciously crafted MP3 file can lead to a potentially exploitable crash. Linux is the only affected platform, so Windows and OS X users are safe from this particular vulnerability.
a use-after-free scenario when playing certain audio files (...) can lead to a potentially exploitable crash
It has been reported that the crash always happen when playing J.Bieber stuff.
Slashdot, fix the reply notifications... You won't get away with it...
It's not really a Firefox / Thunderbird issue if a plugin causes it.
There's tons of plugins out there and in general they aren't of the same quality as Firefox itself. So nothing to see here.
Shouldn't there be a law forbidding the use of low-level languages like C or C++ to build critical applications to avoid such common insiduous and catastrophic flaws like that ?
This is why it's important to have royalty-free codecs for the web that everyone is free to implement. You can choose to do your own implementation of a given codec and take direct responsibility for the security of the implementation, or ship your preferred choice of third-party implementation directly integrated with your product without any patent licensing hassle. I just hope Opus audio and NetVC video become ubiquitous sooner rather than later.
but, but, I know that Linux is always secure, I read it on /.
Anyone have a good way to shut this off? Remove fluendo?
Fed ex of Slashvertisements!
Did I say 'ex'. I meant 'up'!
Imagine that.
I'm looking on Linux Mint and the gstreamer@v@-fluendo-mp3 package is not installed. But I'm still wondering if the other gstreamer library packages (plugins-bad/base/good/etc) that include dozens and dozens of codecs include this anyway.
Or a better question: Does firefox package this along with the browser? Can it be disabled, removed?
I best get removing the guilty parties.
Personally, I blame systemd for this.
If we weren't all either bitching about systemd on the web, or fixing systemd's failings, someone might have got this earlier.
Any more that means the media have nothing else to scream about so trivial issues become "critical".
But only on an open source operating system, in an open source browser.
I guess the quality of software written for closed source operating systems and browsers is just better.
Time to sandbox every data stream in a separate sandbox.
This OS does it from the ground up.
http://genode.org/
Linux is the only affected platform, so Windows and OS X users are safe from this particular vulnerability.
The fact that this is Linux only and not Windows or OS X really should be in the headline! Although I use Linux, this key element makes the news about 21% as important. (Write me back and I will explain the complex equation by which I arrived at that figure.) ;-)
Heartbleed.
Yeah, I'm not totally sure myself, but it seems to me it's not even available on Gentoo, where we use the MAD Gstreamer decoder plugin for MP3 decoding...
From http://fedoraproject.org/wiki/Installing_the_Fluendo_MP3_plugin the plugin should be located at: /usr/lib/gstreamer-1.0/libgstflump3dec.so (and I don't have it, even with gst-plugins-bad and media-libs/gst-plugins-ugly installed).
From https://bugs.gentoo.org/show_bug.cgi?id=281083 they say the plugin was included in gst-plugins-bad, but this dates back to 2009, so things may have changed...
Hmmmm... http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/tree/gst/mpegdemux actually says the plugin originated from Fluendo, but is this really the version talked about in the very (intentionally?) limited report, or a simple fork for which the issue may have been fixed long ago, while not fixed in the official Fluendo version which apparently few really use?
Or does Mozilla ships the plugin themselves? It does not seem to be included in the files installed by Firefox on Gentoo, unless it's been statically linked inside some other file... Even if Mozilla ships it, it's very possible Gentoo does not install it, to use the libraries available on the system...
The Mozilla bug report is still private even though the fix is supposed to be already shipped in Firefox 37...
The relation between Fluendo and Gstreamer is quite blurry too... They employed the main Gstreamer devs for some time, then they left and founded another company, but gstreamer.com is still owned by Fluendo, but they link to the Freedesktop servers to get Gstreamer...
This is actually a little less malicious than you'd think. Firefox has been known to crash when attempting to play HTML5 audio directly to your operating system's media handling framework. You can turn it off and go back to default behavior by going to about:config and turning off media.gstreamer.* or media.windows-media-foundation.*
What do you expect when Mozilla staff are focused on creating a Swiss army knife of a browser (sound like Netscape anybody)? They roll video and audio playback, chat, and other frills into the core and leave it to extensions to fix core functionality issues. Of course the more complicated they make the browser, the more vulnerabilities it will have. Who here remembers when Seamonkey was the only Mozilla product and the dumped it for Firefox because then Firefox was only a 4 MB download? It's time to clean house again.
This is like blaming Windows because a user downloads cracked files filled with malware. You have to purposefully download or run untrusted mp3s. This isn't a linux wide thing, it's a "vulnerability" in a browser based on a plugin. That's pretty deep down the rabbit hole to blame an OS for, aside from that this isn't even a very exploitable bug aside from causing crashing.
https://www.owasp.org/index.php/Using_freed_memory
It seems completely ingrained in my system. How do I get rid of it?
And closed-source OSs don't suffer the same problem.
Imagine that!
There are other GStreamer plugins that provide mp3 playback and don't depend on Fluendo's bullshit.
Could someone provide a link to an MP3 from an untrusted random site that I can listen to which explains how this vulnerability work? Reading is hard!