etcd up to 3.3.22/3.4.9 Permission Check os.MkdirAll permissions

Summaryinfo

A vulnerability classified as critical has been found in etcd up to 3.3.22/3.4.9. This impacts the function os.MkdirAll of the component Permission Check. Performing a manipulation results in permissions. This vulnerability was named CVE-2020-15113. The attack needs to be approached locally. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in etcd up to 3.3.22/3.4.9. It has been classified as problematic. This affects the function os.MkdirAll of the component Permission Check. The manipulation with an unknown input leads to a permissions vulnerability. CWE is classifying the issue as CWE-281. The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In etcd before versions 3.3.23 and 3.4.10, certain directory paths are created (etcd data directory and the directory path when provided to automatically generate self-signed certificates for TLS connections with clients) with restricted access permissions (700) by using the os.MkdirAll. This function does not perform any permission checks when a given directory path exists already. A possible workaround is to ensure the directories have the desired permission (700).

The weakness was presented 08/05/2020 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-15113 since 06/25/2020. The exploitability is told to be difficult. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

Upgrading to version 3.3.23 or 3.4.10 eliminates this vulnerability.

See VDB-159332 and VDB-159331 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• etcd

Version

• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.3.13
• 3.3.14
• 3.3.15
• 3.3.16
• 3.3.17
• 3.3.18
• 3.3.19
• 3.3.20
• 3.3.21
• 3.3.22
• 3.4.0
• 3.4.1
• 3.4.2
• 3.4.3
• 3.4.4
• 3.4.5
• 3.4.6
• 3.4.7
• 3.4.8
• 3.4.9

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