containerd up to 1.3.0 insufficiently protected credentials

Summaryinfo

A vulnerability, which was classified as problematic, was found in containerd up to 1.2/1.2.14/1.2.x/1.3/1.3.0. This affects an unknown part. The manipulation results in insufficiently protected credentials. This vulnerability is known as CVE-2020-15157. It is possible to launch the attack remotely. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in containerd up to 1.2/1.2.14/1.2.x/1.3/1.3.0 (Virtualization Software). It has been classified as problematic. Affected is some unknown functionality. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality.

The weakness was published 10/16/2020. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2020-15157. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1552.

Upgrading to version 1.2.14 or 1.3.0 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Virtualization Software

Name

• containerd

Version

• 1.0
• 1.1
• 1.2
• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5
• 1.2.6
• 1.2.7
• 1.2.8
• 1.2.9
• 1.2.10
• 1.2.11
• 1.2.12
• 1.2.13
• 1.2.14
• 1.3
• 1.3.0

Website

• Product: https://github.com/containerd/containerd/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion