<?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">Security update for docker</DocumentTitle>
  <DocumentType>SUSE Patch</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE-SU-2025:20110-1</ID>
    </Identification>
    <Status>Final</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2025-02-03T09:19:38Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2025-02-03T09:19:38Z</InitialReleaseDate>
    <CurrentReleaseDate>2025-02-03T09:19:38Z</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">Security update for docker</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">This update for docker fixes the following issues:

- Update docker-buildx to v0.19.2. See upstream changelog online at
  &lt;https://github.com/docker/buildx/releases/tag/v0.19.2&gt;.

  Some notable changelogs from the last update:
    * &lt;https://github.com/docker/buildx/releases/tag/v0.19.0&gt;
    * &lt;https://github.com/docker/buildx/releases/tag/v0.18.0&gt;

- Add a new toggle file /etc/docker/suse-secrets-enable which allows users to
  disable the SUSEConnect integration with Docker (which creates special mounts
  in /run/secrets to allow container-suseconnect to authenticate containers
  with registries on registered hosts). bsc#1231348 bsc#1232999

  In order to disable these mounts, just do

    echo 0 &gt; /etc/docker/suse-secrets-enable

  and restart Docker. In order to re-enable them, just do

    echo 1 &gt; /etc/docker/suse-secrets-enable

  and restart Docker. Docker will output information on startup to tell you
  whether the SUSE secrets feature is enabled or not.

- Remove DOCKER_NETWORK_OPTS from docker.service. This was removed from
  sysconfig a long time ago, and apparently this causes issues with systemd in
  some cases.

- Update to docker-buildx v0.17.1 to match standalone docker-buildx package we
  are replacing. See upstream changelog online at
  &lt;https://github.com/docker/buildx/releases/tag/v0.17.1&gt;

- Add %{_sysconfdir}/audit/rules.d to filelist.

- Update to Docker 26.1.5-ce. See upstream changelog online at
  &lt;https://docs.docker.com/engine/release-notes/26.1/#2615&gt;
  bsc#1230294
- This update includes fixes for:
  * CVE-2024-41110. bsc#1228324
  * CVE-2023-47108. bsc#1217070
  * CVE-2023-45142. bsc#1228553
</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">SUSE-SLE-Micro-6.0-169</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/update/announcement/2025/suse-su-202520110-1/</URL>
      <Description>Link for SUSE-SU-2025:20110-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://lists.suse.com/pipermail/sle-security-updates/2025-June/021212.html</URL>
      <Description>E-Mail link for SUSE-SU-2025:20110-1</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/security/rating/</URL>
      <Description>SUSE Security Ratings</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1217070</URL>
      <Description>SUSE Bug 1217070</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1228324</URL>
      <Description>SUSE Bug 1228324</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1228553</URL>
      <Description>SUSE Bug 1228553</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1229806</URL>
      <Description>SUSE Bug 1229806</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1230294</URL>
      <Description>SUSE Bug 1230294</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1230331</URL>
      <Description>SUSE Bug 1230331</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1230333</URL>
      <Description>SUSE Bug 1230333</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1231348</URL>
      <Description>SUSE Bug 1231348</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1232999</URL>
      <Description>SUSE Bug 1232999</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://bugzilla.suse.com/1233819</URL>
      <Description>SUSE Bug 1233819</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2023-45142/</URL>
      <Description>SUSE CVE CVE-2023-45142 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2023-47108/</URL>
      <Description>SUSE CVE CVE-2023-47108 page</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/security/cve/CVE-2024-41110/</URL>
      <Description>SUSE CVE CVE-2024-41110 page</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="SUSE Linux Micro 6.0">
      <Branch Type="Product Name" Name="SUSE Linux Micro 6.0">
        <FullProductName ProductID="SUSE Linux Micro 6.0" CPE="cpe:/o:suse:sl-micro:6.0">SUSE Linux Micro 6.0</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="docker-26.1.5_ce-1.1">
      <FullProductName ProductID="docker-26.1.5_ce-1.1">docker-26.1.5_ce-1.1</FullProductName>
    </Branch>
    <Relationship ProductReference="docker-26.1.5_ce-1.1" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Micro 6.0">
      <FullProductName ProductID="SUSE Linux Micro 6.0:docker-26.1.5_ce-1.1">docker-26.1.5_ce-1.1 as a component of SUSE Linux Micro 6.0</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">OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. A handler wrapper out of the box adds labels `http.user_agent` and `http.method` that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent to it. HTTP header User-Agent or HTTP method for requests can be easily set by an attacker to be random and long. The library internally uses `httpconv.ServerRequest` that records every value for HTTP `method` and `User-Agent`. In order to be affected, a program has to use the `otelhttp.NewHandler` wrapper and not filter any unknown HTTP methods or User agents on the level of CDN, LB, previous middleware, etc. Version 0.44.0 fixed this issue when the values collected for attribute `http.request.method` were changed to be restricted to a set of well-known values and other high cardinality attributes were removed. As a workaround to stop being affected, `otelhttp.WithFilter()` can be used, but it requires manual careful configuration to not log certain requests entirely. For convenience and safe usage of this library, it should by default mark with the label `unknown` non-standard HTTP methods and User agents to show that such requests were made but do not increase cardinality. In case someone wants to stay with the current behavior, library API should allow to enable it.</Note>
    </Notes>
    <CVE>CVE-2023-45142</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Micro 6.0:docker-26.1.5_ce-1.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <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>https://www.suse.com/support/update/announcement/2025/suse-su-202520110-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2023-45142.html</URL>
        <Description>CVE-2023-45142</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1228553</URL>
        <Description>SUSE Bug 1228553</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">OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version 0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent. An attacker can easily flood the peer address and port for requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`.</Note>
    </Notes>
    <CVE>CVE-2023-47108</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Micro 6.0:docker-26.1.5_ce-1.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
    <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>https://www.suse.com/support/update/announcement/2025/suse-su-202520110-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2023-47108.html</URL>
        <Description>CVE-2023-47108</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1217070</URL>
        <Description>SUSE Bug 1217070</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">Moby is an open-source project created by Docker for software containerization. A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low.

Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.

Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.

docker-ce v27.1.1 containes patches to fix the vulnerability. Patches have also been merged into the master, 19.03, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. If one is unable to upgrade immediately, avoid using AuthZ plugins and/or restrict access to the Docker API to trusted parties, following the principle of least privilege.</Note>
    </Notes>
    <CVE>CVE-2024-41110</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>SUSE Linux Micro 6.0:docker-26.1.5_ce-1.1</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>critical</Description>
      </Threat>
    </Threats>
    <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>https://www.suse.com/support/update/announcement/2025/suse-su-202520110-1/</URL>
      </Remediation>
    </Remediations>
    <References>
      <Reference>
        <URL>https://www.suse.com/security/cve/CVE-2024-41110.html</URL>
        <Description>CVE-2024-41110</Description>
      </Reference>
      <Reference>
        <URL>https://bugzilla.suse.com/1228324</URL>
        <Description>SUSE Bug 1228324</Description>
      </Reference>
    </References>
  </Vulnerability>
</cvrfdoc>
