libcgroup up to 0.41 /var/log/cgred information disclosure

Summaryinfo

A vulnerability, which was classified as problematic, has been found in libcgroup up to 0.41. Affected by this issue is some unknown functionality of the file /var/log/cgred. This manipulation causes information disclosure. This vulnerability appears as CVE-2018-14348. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in libcgroup up to 0.41. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /var/log/cgred. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

libcgroup up to and including 0.41 creates /var/log/cgred with mode 0666 regardless of the configured umask, leading to disclosure of information.

The bug was discovered 08/15/2018. The weakness was presented 08/14/2018 (Website). The advisory is shared at lists.fedoraproject.org. This vulnerability is known as CVE-2018-14348 since 07/17/2018. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation needs a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 112048 (Debian DLA-1472-1 : libcgroup security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 171462 (SUSE Enterprise Linux Security Update for libcgroup (SUSE-SU-2018:2468-1)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 7 days after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (112048). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• libcgroup

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.20
• 0.21
• 0.22
• 0.23
• 0.24
• 0.25
• 0.26
• 0.27
• 0.28
• 0.29
• 0.30
• 0.31
• 0.32
• 0.33
• 0.34
• 0.35
• 0.36
• 0.37
• 0.38
• 0.39
• 0.40
• 0.41

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion