Homepage
About Snyk

Exposure of Resource to Wrong Sphere Affecting docker-bash-completion package, versions <20.10.6_ce-6.49.3

Severity

 Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating

    Threat Intelligence

    EPSS
    0.12% (48th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-SLES151-DOCKERBASHCOMPLETION-2674755
  • published 14 Apr 2022
  • disclosed 11 Jun 2021
Report a new vulnerability Found a mistake?

Introduced: 11 Jun 2021

CVE-2021-21334 Open this link in a new tab
CWE-668 Open this link in a new tab

How to fix?

Upgrade SLES:15.1 docker-bash-completion to version 20.10.6_ce-6.49.3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream docker-bash-completion package and not the docker-bash-completion package as distributed by SLES. See How to fix? for SLES:15.1 relevant fixed versions and status.

In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd's CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.

References

CVSS Scores

version 3.1
Expand this section

NVD

6.3 medium
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    High
  • Privileges Required (PR)
    Low
  • User Interaction (UI)
    None
  • Scope (S)
    Changed
  • Confidentiality (C)
    High
  • Integrity (I)
    None
  • Availability (A)
    None
Expand this section

SUSE

6.3 medium
Expand this section

Red Hat

6.3 medium