libX11 has multiple vulnerabilities


Hey, is anyone able to advise whether it’s OK to port libX11 to
libX11 has multiple vulnerabilities:
CVE: CVE-2018-14600
CVE: CVE-2018-14599
CVE: CVE-2018-14598



Few applications use Xlib directly; rather, they employ other libraries that use Xlib functions to provide widget toolkits: Few applications use Xlib directly; rather, they employ other libraries that use Xlib functions to provide [widget toolkits](

And then, the other libraries have multiple vulnerabilities, and then, the toolkits and scripting frameworks have yet more vulnerabilities… etc. And then, Intel CPUs have multiple vulnerabilities :slight_smile:


I’m surprised that there has not been more noise, at least where I look, on the Intel CPU backdoors. Complete bypass according to Toms Hardware who’s citing Christopher Domas at the Black Hat conference in Las Vegas.

“… direct ring 3 to ring 0 hardware privilege escalation … with unrestricted access to the x86.”


It’s probably because there’s a fix for the meltdown and spectre flaws for Freebsd but they really should never have been there in the first place. It’s shoddy work on Intels part.


I don’t think it’s “shoddy work”. I suspect it’s engineers were well aware of the potential risks but were ordered to shut the hell up and provide.

Because without these vulnerabilities Intel CPU’s performance would have been much less and that would have made competition (AMD) look comparatively better. I think Intel sacrificed security to performance initially knowingly and later-on thought that nobody would find out and just continued with the practise.


That’s even worse to know about it and continue. I just gave them the benefit of the doubt though. I like to think that a business like that actually wants to release good products.


Priority 1 for any business is to make money when that business is publicly traded it is there to make money for the shareholders and that is by law. Creating a good product is not their goal that is a side effect of their goal (which is to make money).


strange as it may seem to some people, the primary business of business is to make money. Publicly traded or private.
I have no comment about Intel and the vulnerabilities.


I recently updated my baseboard BIOS to the latest side-channel mitigation version.
For Spectre 2, it seemed I needed to manually set the variable hw.ibrs_disable false
sysctl hw.ibrs_disable=0
to prevent services from being able to disable the restricted speculation on-the-fly.
However, to persistently achieve the states:
sysctl hw.ibrs_active 1
sysctl hw.ibrs_disable 0
I needed to edit
with an addition


@tqfs A note, when I said backdoor I meant backdoor. This is an entirely different problem than the spectre etc holes.


Dark Hat Presentation (12 pages from the bottom):