01.28.15

Qualys Starts Self-Promotional FUD Campaign, Naming a Bug That Was Already Fixed 2 Years Ago and Distros Have Covered With Patches

Posted in FUD, GNU/Linux, Google, Red Hat, Security, Ubuntu at 12:23 pm by Dr. Roy Schestowitz

Ghostwriting a Qualys horror story for maximal FUD (fear, uncertainty, and doubt)

Spooky

Summary: Responding to the media blitz which paints GNU/Linux as insecure despite the fact that bugs were evidently found and fixed

THERE IS something to be said about the “top” news regarding GNU/Linux. It’s not really news. The so-called “GHOST” publicity stunt needn’t be repeated by FOSS sites. It is about a bug which was patched two years ago, but some sites overlook this important fact and stick lots of spooky logos, playing right into the hands of Qualys, an insecurity firm (making money from lack of security or perception of insecurity).

We have watches the ‘news’ unfolding over the past day and a half and now is a good time to explain what we deal with. The so-called “GHOST” (all capital letters!) bug is old. Qualys is going two years ago into bugfixes, giving a name to the bugfixes, then making plenty of noise (all over the news right now). Qualys does not look like a proxy of Microsoft or other GNU/Linux foes, but it is self-serving. Insecurity firms like Qualys probably learned that giving a name to a bug in GNU (SJVN mistakenly calls it “Linux”, but so do many others) would give more publicity and people will pay attention to brands and logos rather than to substance. Just before Christmas an insecurity firm tried to do that with "Grinch" and it turned out to be a farce. SJVN says that this old “vulnerability enables hackers to remotely take control of systems without even knowing any system IDs or passwords.”

Well, it was patched back in 2013. Use of names for marketing is what makes it “news”; the opportunists even prepared a PRESS RELEASE and pushed it into ‘big’ sites like CNN. It has marketing written all over it, just like “Heartbleed” that had strong Microsoft connections behind the disclosure. It is sad that Linux sites fall for this. Phoronix copies the press release as though it’s reliable rather than self-promotional. Michael Larabel writes: “The latest high-profile security vulnerability affecting Linux systems us within Glibc, the GNU C Library.”

It is not “latest”, it is 2 years old. Larabel says that “Qualys found that the bug had actually been patched with a minor bug fix released on May 21, 2013 between the releases of glibc-2.17 and glibc-2.18.”

OK, so it’s not news. FOSS Force cites SJVN to amplify the scare and other FOSS sites are playing along as though this is top news. It oughtn’t be. It is already widely patched (maybe requiring a reboot), so let’s patch and move on (unless it was already patched upstream/downstream years ago). IDG has already published at least three articles about it [1, 2], including one from Swapnil Bhartiya, who is not too alarmist to his credit. He noted that “there was a patch released back on May 21, 2013, between the releases of glibc-2.17 and glibc-2.18. However it was not considered to be a security risk and thus major Linux distributions that offer long term support and get security updates remained vulnerable, including Debian 7 (wheezy), Red Hat Enterprise Linux 6 & 7, CentOS 6 & 7 and Ubuntu 12.04.”

It affects very specific versions, mostly long-term support releases that already have reliable patches available. It should be clear that some headlines such as this or that clarify the limited scope of impact (not bad reporting) unlike the alarmist trolls.

What Techrights generally found was that early coverage came from so-called ‘security’ sites or blogs of insecurity firms that try to sell their services (e.g. [1, 2, 3]). These set the tone for many.

The response to this bug is proportional to the perceived danger (e.g. due to media hype), not the severity of the bug. Some security news sites [1, 2] focus on names and logos while facts remain only a side issue. This so-called “ghost” nonsense (some lines of code basically) was fixed 2 years ago and as the blog post “long term support considered harmful” explains it: “In theory, somebody at glibc should have noticed that fixing a buffer flow in a function that parses network data has security implications. That doesn’t always happen, however, for many reasons. Sometimes the assessment isn’t made; sometimes the assessment fails to consider all possible exploit strategies. Security bugs are “silently” fixed frequently enough (without evil intentions) that we should consider them a fact of life and deal with them accordingly.”

Some of the worst kind of coverage we found came from The Register with its flamebait headlines (scary headlines for maximum effect) and the troll Brian Fagioli. They are only some among many who are using the name to come up with puns and FUD. Jim Finkle is back to his GNU/Linux-hostile ‘reporting’, bringing this to the corporate media (there is some in the UK also) and LWN quickly cited the GNU/Linux-hostile Dan Goodin. He called “Highly critical” a bug that was patched two years ago.

Debunking some of the latest security FUD we had Fedora Magazine which stated “don’t be [worried], on supported Fedora versions.”

For unsupported version there is a lot more than this one bug that one needs to worry about.

Apple fans were quick to take advantage of the news, despite the fact that Apple is leaving systems vulnerable for many months, knowingly (like Microsoft does, until Google steps in).

See, with proprietary systems one knows for a fact that there is no security. With GNU/Linux is an open question and it depends on what measures one takes to keep it secure. For Apple and Microsoft security is not at all the goal; back doors and unpatched flaws are not really as “interesting” and important for them to patch as helping spying agencies. Google is not at fault here, Google just saw that Apple and Microsoft had no plans to plug serious holes — a patch evidently wasn’t going to be made ready before the public finds out about it, owing to Google. Apple chooses to blame Google; same as Microsoft. They should only blame themselves both for the bugs and for negligence after the bugs were highlighted to them. There is no room here for properly comparing GNU/Linux (Free/libre) to OS X or Windows (proprietary) because evidence clearly shows that the latter are not interested in security and not pursuing security when it is trivially possible.

What we find curious amid the latest FUD campaign is that Apple back/bug doors are not as widely publicised as a GNU bug that was patched 2 years ago and mostly affects LTS systems (which already have patches available). “Nothing I can think of,” said a reader of ours about this media hype, “but the LTS model followed by RHEL and Ubuntu have different goals and purposes than the short, fast development cycle like OpenBSD.”

Nobody is forced to use an LTS release and those who choose it must be aware of the potential risk.

Regarding the other FUD that flooded the press in recent weeks, targeting for the most part Google and Android, our reader XFaCE wrote the following:

I assume you want to write about that new Android vulnerability. Basically I can see the narrative being pushed through three points

- Microsoft supported Windows XP/7/etc. for years, why doesn’t Google support old Android versions

- Google told Microsoft about a very old bug in their software, so they are hypocritical

- Heartbleed bug was fixed way back for 4.1.1

For the last point, it’s a bullshit comparison because

a) 4.1.1 was one point release where upgrading to 4.1.2 fixed the issue (it was already fixed back when 4.1.2 was released)

b) The fix was one file, as evident by XDA members patched it themselves on phones manufacturers refused to upgrade to 4.1.2 SOURCE: http://forum.xda-developers.com/showthread.php?t=2712916

c) As shown by the link, a lot of manufacturers DIDN’T update certain 4.1.1 devices to 4.1.2, hence proving Google’s point. The fix there was SIMPLE, but the OEMs didn’t bother to do it

With Webview, not only is webview involved, but so is the webkit rendering engine, so the fix for all those previously releases is much more complicated

As for the second point, Google did catch it, with KitKat, and furthermore made KitKat supported on more low-end devices so theoretically older 512mb or less devices could be updated

For example, HTC said (when Jelly Bean 4.1 came out) that they would not update any device with 512 mb of RAM (SOURCE: http://www.cnet.com/news/htc-one-v-and-desire-c-will-never-get-jelly-bean/ ), so naturally when KitKat came out, they updated those devices because the OS officially was designed for such low ram devices

oh wait

http://www.androidpit.com/android-4-4-kitkat-update-plans

“Later this year, the entry-level smartphone the HTC Desire 500, should also be seeing the KitKat update. However, the One X, One X+, One S, and One V will be left in the dust and will be receiving no more official updates from HTC.”

So the OEMs are at fault for not upgrading the devices, not Google, which leads to point 1 – Google doesn’t control the Android OEMs like Microsoft does OEM pay Microsoft for the support whereby Microsoft controls all updates, Google doesn’t get paid or have the agreemeent in that way

OEMs like HTC could easily fix this by porting Kitkat to those devices, but they won’t cause they want you to buy a new HTC phone or whatever phone brand

Techrights did not cover that (except in daily links) because it should be self-evident that free-of-charge Android upgrades make it inhernetly different from proprietary software and keeping up to data typically ensures security. A lot of the analogies (Android and Windows) were inherently flawed and the FUD rather shallow.

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. Links 28/1/2021: Stable Kernels and Sudo Bugfixes

    Links for the day



  2. Showing Solidarity With FSFE Survivors

    What does justice look like?



  3. IBM is Throwing Away Red Hat's 'de Facto Standard' Status in Servers, Wrongly Assuming People Can't (or Won't) Go Elsewhere

    This new video is over half an hour long and it’s a discussion of IBM’s self-harming (shot-in-the-foot) move, which it already seems to regret



  4. Why 6 Screens and 6 Virtual Desktops

    An explanation of how I use computers and how I distribute tasks (across screens and across virtual desktops)



  5. Red Hat Developer Network Promoting Microsoft's Proprietary Software, Sometimes by Mass-Mailing People

    Red Hat is doing a disservice to people who subscribe to E-mail newsletters; those people are almost never into Microsoft's proprietary software, which they want to get away from



  6. IRC Proceedings: Tuesday, January 26, 2021

    IRC logs for Tuesday, January 26, 2021



  7. Links 26/1/2021: Mozilla Firefox 85.0, Tails 4.15, Zentyal Server 7.0, GNOME 40 Alpha

    Links for the day



  8. Instead of Making Access to COVID-19 Solutions Easier Bill Gates Has Made It Harder (Patent Profits)

    Counterproductively — and at a great cost to human civilisation — Bill Gates has once again put profits and monopoly ahead of global goals such as collective health



  9. We Need More Documents Leaked to Know Intel (From the) Inside

    We invite more leaks from the belly of the beast "chipzilla", seeing that it is becoming a drone of Microsoft again, yearning for the "Wintel" days instead of moving on to a world dominated by GNU/Linux and Free/libre software



  10. Why GNU/Linux Users (and the Public at Large) Should Support Leaking/Whistleblowing Sites (Including Wikileaks)

    To demonstrate the value of "scientific journalism" (a term apparently coined by Wikileaks) we take a look at Red Hat's response to embarrassing leaks (demonstrating what a scam their certification and examination programmes really are)



  11. EPO President António Campinos is Still Not Listening, According to Internal EPO Documents

    Increasingly arrogant and unaccountable management of Europe's second-largest institution (EPO) has left staff disillusioned but still defiant; there's clearly unsuitable or unfit-for-purpose management at the EPO, self-selecting based on nepotism/loyalty so as to cover up abuses



  12. Why You Should Give Falkon (the Web Browser) a Chance on GNU/Linux, BSD, or Windows

    In this crazy new world where advertisers are the real customers and Web users ("audiences") have been reduced to mere products we need a browser that isn't controlled by a company; try Falkon



  13. Kluwer Patent Spin and Distortion of Facts (Regarding UPC and More)

    Kluwer Patent Blog disgraces the firm that puts its name on it; instead of sticking to facts they're distorting the facts and the sole/principal goal is to manipulate/mislead the public and public servants



  14. Links 26/1/2021: 4MLinux 35.1, GParted 1.2, Gnuastro 0.14

    Links for the day



  15. IRC Proceedings: Monday, January 25, 2021

    IRC logs for Monday, January 25, 2021



  16. It's Wrong to Assume Red Hat Competes With Microsoft

    The community ought to stop pretending that one monopoly seeks to replace another despite close partnerships (some would say "collusion") between the two



  17. EPO Staff Representation Complains That EPO Management Exploits Pandemic and 'House Arrests' to Overwork Staff, Lower Quality

    The EPO keeps breaking its promises to workers; not only are key employees seeing their net salary cut (inflation factored in) but pensioners too are being robbed and in the meantime the total time spent on work is increasing



  18. Fake News is Not a 'Wing' Thing

    The two-party corporate-led system (and media) would have us obsess/bicker about accuracy of news based on some binary/dual system of blind loyalty rather than underlying facts and priorities



  19. Links 25/1/2021: Huawei on GNU/Linux, NuTyX 20.12.1, Whisker Menu 2.5.3, Lutris 0.5.8.3, Linux 5.11 RC5

    Links for the day



  20. Fear, Uncertainty, and Doubt (FUD) in ZDNet is the Norm

    ZDNet continues to emit lots of garbage 'journalism', in effect Microsoft PR and what's known as "black PR" for Linux; just like Bleeping Computer, which ZDNet hired this writer from, there's no adherence to facts, just smears and innuendo



  21. Truth Tellers Aren't an Enemy of Free Software

    There's a perpetual attack on people who speak out against actors and corporations in positions of great power, however subtle and indirect those attacks may seem on the surface (they don't wish to be held accountable for defaming activists)



  22. The Linux Foundation, With Over 124 Million Dollars in Annual Revenue, is in Trouble Because of the Pandemic, So It's Trying to Reinvent Itself as Training and Certifications Outfit

    With mountains of cash and a Public Relations (PR) or marketing business model the so-called 'Linux' Foundation became reliant on travel, lodging, booths and speeches on sale; COVID-19 is a great risk to that business model



  23. IRC Proceedings: Sunday, January 24, 2021

    IRC logs for Sunday, January 24, 2021



  24. Our Move Further Away From the World Wide Web, the Browser Monopolies, HTTP, and HTML

    The World Wide Web (WWW) is going down a bad path and a clearly regressive direction; the solution isn't going 'retro' but exploring more sophisticated systems which are robust to censorship (localised or globalised) and downtime (related to censorship) while reducing surveillance by leveraging encryption at the endpoints



  25. Important Issues Not Entertained in the Community, Especially Critics of the Status Quo

    here's corporate infiltration inside communities (for oligarchy hunts volunteer, unpaid labour) and those who speak about that as a threat to our cause and objectives are painted as misguided outcasts who must be ignored



  26. Internet Origins of the Mob

    Reprinted with permission from Daniel Pocock



  27. When Proprietary Software Users Dictate the Freedom-Leaning Communities

    Fedora doesn't care about software freedom and its steward (or parent company) is sometimes imposing proprietary software on staff; they've quit caring



  28. In 2020 Onwards 'Open Source' is Just a Marketing Ploy of Monopolies, Unlike Free Software

    More people are nowadays seeing or witnessing 'Open Source' for what it truly is; the term has become a misleading marketing term of proprietary software firms looking to rebrand as "ethical" (e.g. by sharing some code with other proprietary software firms, over proprietary platforms such as GitHub)



  29. Microsoft: The Year After We Bought GitHub There Was a Significant Decline in Number of New Projects on GitHub

    Microsoft has just admitted that in 2019 GitHub saw a very significant decline in number of new projects (and users, which it is conveniently miscounting by adding 'phantom' ones) on the site. Just what we had heard before they confirmed it (and they foresaw this effect of the takeover, hence the lies about "loving" Linux).



  30. Social Control Media is a Passing Fad, We Should All Go Back to Blogging and Subscribing to RSS Feeds

    The whole "social control media" phenomenon has been oversold or promoted using lies; in reality, as a mountain of evidence serves to show, it's a way to manage society at a macro scale


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts