<?xml version="1.0" encoding="UTF-8"?>
<cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
  <DocumentTitle xml:lang="en">docker-20.10.6_ce-2.1 on GA media</DocumentTitle>
  <DocumentType>SUSE Patch</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>openSUSE-SU-2024:10722-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2024-06-15T00:00:00Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2024-06-15T00:00:00Z</InitialReleaseDate>
    <CurrentReleaseDate>2024-06-15T00:00:00Z</CurrentReleaseDate>
    <Generator>
      <Engine>cve-database/bin/generate-cvrf.pl</Engine>
      <Date>2017-02-24T01:00:00Z</Date>
    </Generator>
  </DocumentTracking>
  <DocumentNotes>
    <Note Title="Topic" Type="Summary" Ordinal="1" xml:lang="en">docker-20.10.6_ce-2.1 on GA media</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">These are all security issues fixed in the docker-20.10.6_ce-2.1 package on the GA media of openSUSE Tumbleweed.</Note>
    <Note Title="Terms of Use" Type="Legal Disclaimer" Ordinal="3" xml:lang="en">The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).</Note>
    <Note Title="Patchnames" Type="Details" Ordinal="4" xml:lang="en">openSUSE-Tumbleweed-2024-10722</Note>
  </DocumentNotes>
  <DocumentDistribution xml:lang="en">Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0)</DocumentDistribution>
  <DocumentReferences>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/security/rating/</URL>
      <Description>SUSE Security Ratings</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2016-9962/</URL>
      <Description>SUSE CVE CVE-2016-9962 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2017-14992/</URL>
      <Description>SUSE CVE CVE-2017-14992 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2017-16539/</URL>
      <Description>SUSE CVE CVE-2017-16539 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2018-10892/</URL>
      <Description>SUSE CVE CVE-2018-10892 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2018-15664/</URL>
      <Description>SUSE CVE CVE-2018-15664 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2018-16873/</URL>
      <Description>SUSE CVE CVE-2018-16873 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2018-16874/</URL>
      <Description>SUSE CVE CVE-2018-16874 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2018-16875/</URL>
      <Description>SUSE CVE CVE-2018-16875 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2018-20699/</URL>
      <Description>SUSE CVE CVE-2018-20699 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2019-13509/</URL>
      <Description>SUSE CVE CVE-2019-13509 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2019-14271/</URL>
      <Description>SUSE CVE CVE-2019-14271 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2020-13401/</URL>
      <Description>SUSE CVE CVE-2020-13401 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2020-15257/</URL>
      <Description>SUSE CVE CVE-2020-15257 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2021-21284/</URL>
      <Description>SUSE CVE CVE-2021-21284 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="openSUSE Tumbleweed">
      <Branch Type="Product Name" Name="openSUSE Tumbleweed">
        <FullProductName ProductID="openSUSE Tumbleweed" CPE="cpe:/o:opensuse:tumbleweed">openSUSE Tumbleweed</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="docker-20.10.6_ce-2.1">
      <FullProductName ProductID="docker-20.10.6_ce-2.1">docker-20.10.6_ce-2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="docker-bash-completion-20.10.6_ce-2.1">
      <FullProductName ProductID="docker-bash-completion-20.10.6_ce-2.1">docker-bash-completion-20.10.6_ce-2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="docker-fish-completion-20.10.6_ce-2.1">
      <FullProductName ProductID="docker-fish-completion-20.10.6_ce-2.1">docker-fish-completion-20.10.6_ce-2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="docker-zsh-completion-20.10.6_ce-2.1">
      <FullProductName ProductID="docker-zsh-completion-20.10.6_ce-2.1">docker-zsh-completion-20.10.6_ce-2.1</FullProductName>
    </Branch>
    <Relationship ProductReference="docker-20.10.6_ce-2.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:docker-20.10.6_ce-2.1">docker-20.10.6_ce-2.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="docker-bash-completion-20.10.6_ce-2.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1">docker-bash-completion-20.10.6_ce-2.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="docker-fish-completion-20.10.6_ce-2.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1">docker-fish-completion-20.10.6_ce-2.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="docker-zsh-completion-20.10.6_ce-2.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1">docker-zsh-completion-20.10.6_ce-2.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
  </ProductTree>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="1">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container.  This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container.</Note>
    </Notes>
    <CVE>CVE-2016-9962</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>4.1</BaseScore>
        <Vector>AV:L/AC:M/Au:S/C:P/I:P/A:P</Vector>
      </ScoreSet>
      <ScoreSet>
        <BaseScore>4.4</BaseScore>
        <Vector>AV:L/AC:M/Au:N/C:P/I:P/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2016-9962.html</URL>
        <Description>CVE-2016-9962</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1012568</URL>
        <Description>SUSE Bug 1012568</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1173425</URL>
        <Description>SUSE Bug 1173425</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="2">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">Lack of content verification in Docker-CE (Also known as Moby) versions 1.12.6-0, 1.10.3, 17.03.0, 17.03.1, 17.03.2, 17.06.0, 17.06.1, 17.06.2, 17.09.0, and earlier allows a remote attacker to cause a Denial of Service via a crafted image layer payload, aka gzip bombing.</Note>
    </Notes>
    <CVE>CVE-2017-14992</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>4.9</BaseScore>
        <Vector>AV:L/AC:L/Au:N/C:N/I:N/A:C</Vector>
      </ScoreSet>
      <ScoreSet>
        <BaseScore>4.3</BaseScore>
        <Vector>AV:N/AC:M/Au:N/C:N/I:N/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2017-14992.html</URL>
        <Description>CVE-2017-14992</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1066210</URL>
        <Description>SUSE Bug 1066210</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="3">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">The DefaultLinuxSpec function in oci/defaults.go in Docker Moby through 17.03.2-ce does not block /proc/scsi pathnames, which allows attackers to trigger data loss (when certain older Linux kernels are used) by leveraging Docker container access to write a "scsi remove-single-device" line to /proc/scsi/scsi, aka SCSI MICDROP.</Note>
    </Notes>
    <CVE>CVE-2017-16539</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>3.6</BaseScore>
        <Vector>AV:L/AC:L/Au:N/C:N/I:P/A:P</Vector>
      </ScoreSet>
      <ScoreSet>
        <BaseScore>4.3</BaseScore>
        <Vector>AV:N/AC:M/Au:N/C:N/I:N/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2017-16539.html</URL>
        <Description>CVE-2017-16539</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1066801</URL>
        <Description>SUSE Bug 1066801</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="4">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">The default OCI linux spec in oci/defaults{_linux}.go in Docker/Moby from 1.11 to current does not block /proc/acpi pathnames. The flaw allows an attacker to modify host's hardware like enabling/disabling bluetooth or turning up/down keyboard brightness.</Note>
    </Notes>
    <CVE>CVE-2018-10892</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>5</BaseScore>
        <Vector>AV:N/AC:L/Au:N/C:N/I:P/A:N</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2018-10892.html</URL>
        <Description>CVE-2018-10892</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1100331</URL>
        <Description>SUSE Bug 1100331</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1100838</URL>
        <Description>SUSE Bug 1100838</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="5">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Docker through 18.06.1-ce-rc2, the API endpoints behind the 'docker cp' command are vulnerable to a symlink-exchange attack with Directory Traversal, giving attackers arbitrary read-write access to the host filesystem with root privileges, because daemon/archive.go does not do archive operations on a frozen filesystem (or from within a chroot).</Note>
    </Notes>
    <CVE>CVE-2018-15664</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>6.2</BaseScore>
        <Vector>AV:L/AC:H/Au:N/C:C/I:C/A:C</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2018-15664.html</URL>
        <Description>CVE-2018-15664</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1096726</URL>
        <Description>SUSE Bug 1096726</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1139649</URL>
        <Description>SUSE Bug 1139649</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="6">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands, they will execute on the system running "go get -u".</Note>
    </Notes>
    <CVE>CVE-2018-16873</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>6.8</BaseScore>
        <Vector>AV:N/AC:M/Au:N/C:P/I:P/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2018-16873.html</URL>
        <Description>CVE-2018-16873</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118897</URL>
        <Description>SUSE Bug 1118897</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118898</URL>
        <Description>SUSE Bug 1118898</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118899</URL>
        <Description>SUSE Bug 1118899</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="7">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go package which contains curly braces (both '{' and '}' characters). Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). The attacker can cause an arbitrary filesystem write, which can lead to code execution.</Note>
    </Notes>
    <CVE>CVE-2018-16874</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>6.8</BaseScore>
        <Vector>AV:N/AC:M/Au:N/C:P/I:P/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2018-16874.html</URL>
        <Description>CVE-2018-16874</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118897</URL>
        <Description>SUSE Bug 1118897</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118898</URL>
        <Description>SUSE Bug 1118898</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118899</URL>
        <Description>SUSE Bug 1118899</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="8">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.</Note>
    </Notes>
    <CVE>CVE-2018-16875</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>7.8</BaseScore>
        <Vector>AV:N/AC:L/Au:N/C:N/I:N/A:C</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2018-16875.html</URL>
        <Description>CVE-2018-16875</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118897</URL>
        <Description>SUSE Bug 1118897</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118898</URL>
        <Description>SUSE Bug 1118898</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1118899</URL>
        <Description>SUSE Bug 1118899</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="9">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">Docker Engine before 18.09 allows attackers to cause a denial of service (dockerd memory consumption) via a large integer in a --cpuset-mems or --cpuset-cpus value, related to daemon/daemon_unix.go, pkg/parsers/parsers.go, and pkg/sysinfo/sysinfo.go.</Note>
    </Notes>
    <CVE>CVE-2018-20699</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>4</BaseScore>
        <Vector>AV:N/AC:L/Au:S/C:N/I:N/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2018-20699.html</URL>
        <Description>CVE-2018-20699</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1121768</URL>
        <Description>SUSE Bug 1121768</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="10">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Docker CE and EE before 18.09.8 (as well as Docker EE before 17.06.2-ee-23 and 18.x before 18.03.1-ee-10), Docker Engine in debug mode may sometimes add secrets to the debug log. This applies to a scenario where docker stack deploy is run to redeploy a stack that includes (non external) secrets. It potentially applies to other API users of the stack API if they resend the secret.</Note>
    </Notes>
    <CVE>CVE-2019-13509</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>5</BaseScore>
        <Vector>AV:N/AC:L/Au:N/C:P/I:N/A:N</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2019-13509.html</URL>
        <Description>CVE-2019-13509</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1142160</URL>
        <Description>SUSE Bug 1142160</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="11">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Docker 19.03.x before 19.03.1 linked against the GNU C Library (aka glibc), code injection can occur when the nsswitch facility dynamically loads a library inside a chroot that contains the contents of the container.</Note>
    </Notes>
    <CVE>CVE-2019-14271</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>7.5</BaseScore>
        <Vector>AV:N/AC:L/Au:N/C:P/I:P/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2019-14271.html</URL>
        <Description>CVE-2019-14271</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1143409</URL>
        <Description>SUSE Bug 1143409</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="12">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">An issue was discovered in Docker Engine before 19.03.11. An attacker in a container, with the CAP_NET_RAW capability, can craft IPv6 router advertisements, and consequently spoof external IPv6 hosts, obtain sensitive information, or cause a denial of service.</Note>
    </Notes>
    <CVE>CVE-2020-13401</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>6</BaseScore>
        <Vector>AV:N/AC:M/Au:S/C:P/I:P/A:P</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2020-13401.html</URL>
        <Description>CVE-2020-13401</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1172375</URL>
        <Description>SUSE Bug 1172375</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1172377</URL>
        <Description>SUSE Bug 1172377</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="13">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim's API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.</Note>
    </Notes>
    <CVE>CVE-2020-15257</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>3.6</BaseScore>
        <Vector>AV:L/AC:L/Au:N/C:P/I:P/A:N</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2020-15257.html</URL>
        <Description>CVE-2020-15257</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1178969</URL>
        <Description>SUSE Bug 1178969</Description>
      </Reference>
    </References>
  </Vulnerability>
  <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="14">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Docker before versions 9.03.15, 20.10.3 there is a vulnerability involving the --userns-remap option in which access to remapped root allows privilege escalation to real root. When using "--userns-remap", if the root user in the remapped namespace has access to the host filesystem they can modify files under "/var/lib/docker/&lt;remapping&gt;" that cause writing files with extended privileges. Versions 20.10.3 and 19.03.15 contain patches that prevent privilege escalation from remapped user.</Note>
    </Notes>
    <CVE>CVE-2021-21284</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:docker-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-bash-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-fish-completion-20.10.6_ce-2.1</ProductID>
        <ProductID>openSUSE Tumbleweed:docker-zsh-completion-20.10.6_ce-2.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>low</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSet>
        <BaseScore>2.7</BaseScore>
        <Vector>AV:A/AC:L/Au:S/C:N/I:P/A:N</Vector>
      </ScoreSet>
    </CVSSScoreSets>
    <Remediations>
      <Remediation Type="Vendor Fix">
        <Description xml:lang="en">To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
</Description>
        <URL/>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2021-21284.html</URL>
        <Description>CVE-2021-21284</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1181732</URL>
        <Description>SUSE Bug 1181732</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
