Multiple Critical Security Vulnerabilities Discovered In Linux Systemd

  • 617
  •  
  •  
  •  
  •  
  •  
  •  
    617
    Shares

Researchers have discovered some serious security flaws threatening Linux. These vulnerabilities exist in Linux systemd component. According to the researchers, the vulnerabilities pose a risk to all systemd-based Linux distros.

Linux Systemd Barraged With Multiple Vulnerabilities

Allegedly, researchers at Qualys have disclosed some bugs targeting the Linux systemd component. Systemd provides the core building blocks for Linux and handles major processes after booting.

As revealed, three vulnerabilities have targeted the systemd-journald, which is responsible for data collection and log storage. The vulnerabilities let an attacker gain root privileges on the target device. The researchers state that these vulnerabilities threaten all Linux distros based on systemd except a few. As stated in their report,

“To the best of our knowledge, all systemd-based Linux distributions are vulnerable, but SUSE Linux Enterprise 15, openSUSE Leap 15.0, and Fedora 28 and 29 are not exploitable because their user space is compiled with GCC’s -fstack-clash-protection.”

The three bugs include two different memory corruption flaws (CVE-2018-16864 and CVE-2018-16865), and an out-of-bounds flaw (CVE-2018-16866). At first, the researchers accidentally discovered CVE-2018-16864 while working on an exploit for a previously disclosed vulnerability, Mutagen Astronomy. Then, when they were busy on its PoC, they spotted the other two bugs.

Patches Coming Soon

At the moment, researchers have not disclosed their exploits. However, they plan to reveal them in near future. Regarding the exploits, they stated,

“We developed a proof of concept for CVE-2018-16864 that gains eip control on i386… We developed an exploit for CVE-2018-16865 and CVE-2018-16866 that obtains a local root shell in 10 minutes on i386 and 70 minutes on amd64, on average.”

Interestingly, the bugs had been around for quite a few years. According to their findings, CVE-2018-16864 came up in April 2013, and CVE-2018-16865 in December 2011. They then became exploitable in February 2016 (systemd v230) and April 2013 (systemd v201). The most recent of these is CVE-2018-16866, which was introduced in June 2015 (systemd v221). Though it received a patch earlier in August 2018, the researchers call it an inadvertent patch.

For now, Red Hat has patched the bugs CVE-2018-16864 and CVE-2018-16865. Whereas, Debian has fixed CVE-2018-16866 in the unstable systemd 240-1 release. Other distros will also supposedly release the fixes soon.

In November 2018, a Google researcher also highlighted a critical flaw in Systemd that induced system crashes and hacks.

The following two tabs change content below.

Abeerah Hashim

Abeerah has been a passionate blogger for several years with a particular interest towards science and technology. She is crazy to know everything about the latest tech developments. Knowing and writing about cybersecurity, hacking, and spying has always enchanted her. When she is not writing, what else can be a better pastime than web surfing and staying updated about the tech world! Reach out to me at: [email protected]

Abeerah Hashim

Abeerah has been a passionate blogger for several years with a particular interest towards science and technology. She is crazy to know everything about the latest tech developments. Knowing and writing about cybersecurity, hacking, and spying has always enchanted her. When she is not writing, what else can be a better pastime than web surfing and staying updated about the tech world! Reach out to me at: [email protected]

Do NOT follow this link or you will be banned from the site!

Privacy Preference Center

Necessary

The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]

Advertising

DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.

doubleclick

Analytics

The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid