<?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">SUSE-IU-2025:570-1</DocumentTitle>
  <DocumentType>SUSE Image</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE Image SUSE-IU-2025:570-1</ID>
    </Identification>
    <Status>Interim</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>1</Number>
        <Date>2025-11-19T17:01:34Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2025-02-10T01:00:00Z</InitialReleaseDate>
    <CurrentReleaseDate>2025-02-10T01:00:00Z</CurrentReleaseDate>
    <Generator>
      <Engine>cve-database/bin/generate-cvrf-publiccloud.pl</Engine>
      <Date>2021-02-18T01:00:00Z</Date>
    </Generator>
  </DocumentTracking>
  <DocumentNotes>
    <Note Title="Topic" Type="Summary" Ordinal="1" xml:lang="en">Image update for SUSE-IU-2025:570-1 / google/sle-micro-6-1-byos-v20250210-arm64</Note>
    <Note Title="Details" Type="General" Ordinal="2" xml:lang="en">This image update for google/sle-micro-6-1-byos-v20250210-arm64 contains the following changes:
Package iptables was updated:

- Add iptables-1.8.9-fix-checking-existence-of-rule.patch  * Fixes checking existence of rules. Fixes issues with rule creation
    with podman/netavark. (bsc#1235088, bsc#1234996)

Package libzypp was updated:

- Url: queryparams without value should not have a trailing &amp;quot;=&amp;quot;.- version 17.35.16 (35)

- Url query part: `=` is a safe char in value (bsc#1234304)
- RpmDb: Recognize rpmdb.sqlite as database file (#593)
- Fix typo (fixes #592)
- cmake: check location of fcgi header and adjust include
  accordingly. On Debian and derivatives the fcgi headers
  are not stored in a fastcgi/ subdirectory.(#590)
- version 17.35.15 (35)

- The 20MB download limit must not apply to non-metadata files like
  package URLs provided via the CLI (bsc#1233393).
- version 17.35.14 (35)

- BuildCache: Don't try to retrieve missing raw metadata if no
  permission to write the cache (bsc#1225451)
- RepoManager: throw RepoNoPermissionException if the user has no
  permission to update(write) the caches (bsc#1225451)
- version 17.35.13 (35)

Package rsync was updated:

- Bump protocol version to 32 - make it easier to show server is patched.  * Add rsync-protocol-version-32.patch

- Fix FLAG_GOT_DIR_FLIST collission with FLAG_HLINKED
  * Added rsync-fix-FLAG_GOT_DIR_FLIST.patch

- Security update,CVE-2024-12747, bsc#1235475 race condition in handling symbolic links
  * Added rsync-CVE-2024-12747.patch

- Security update, fix multiple vulnerabilities:
  * CVE-2024-12084, bsc#1234100 - Heap Buffer Overflow in Checksum Parsing
  * CVE-2024-12085, bsc#1234101 - Info Leak via uninitialized Stack contents defeats ASLR
  * CVE-2024-12086, bsc#1234102 - Server leaks arbitrary client files
  * CVE-2024-12087, bsc#1234103 - Server can make client write files outside of destination directory using symbolic links
  * CVE-2024-12088, bsc#1234104 - --safe-links Bypass
  * Added rsync-CVE-2024-12084-overflow-01.patch
  * Added rsync-CVE-2024-12084-overflow-02.patch
  * Added rsync-CVE-2024-12085.patch
  * Added rsync-CVE-2024-12086_01.patch
  * Added rsync-CVE-2024-12086_02.patch
  * Added rsync-CVE-2024-12086_03.patch
  * Added rsync-CVE-2024-12086_04.patch
  * Added rsync-CVE-2024-12087_01.patch
  * Added rsync-CVE-2024-12087_02.patch
  * Added rsync-CVE-2024-12088.patch

</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>
  </DocumentNotes>
  <DocumentReferences>
    <Reference Type="Self">
      <URL>https://publiccloudimagechangeinfo.suse.com/google/sle-micro-6-1-byos-v20250210-arm64/</URL>
      <Description>Public Cloud Image Info</Description>
    </Reference>
    <Reference Type="Self">
      <URL>https://www.suse.com/support/security/rating/</URL>
      <Description>SUSE Security Ratings</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
    <Branch Type="Product Family" Name="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <Branch Type="Product Name" Name="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
        <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="SL-Micro-release-6.1-slfo.1.11.2">
      <FullProductName ProductID="SL-Micro-release-6.1-slfo.1.11.2">SL-Micro-release-6.1-slfo.1.11.2</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="iptables-1.8.9-slfo.1.1_2.1">
      <FullProductName ProductID="iptables-1.8.9-slfo.1.1_2.1">iptables-1.8.9-slfo.1.1_2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="kernel-default-6.4.0-24.1">
      <FullProductName ProductID="kernel-default-6.4.0-24.1">kernel-default-6.4.0-24.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="libip4tc2-1.8.9-slfo.1.1_2.1">
      <FullProductName ProductID="libip4tc2-1.8.9-slfo.1.1_2.1">libip4tc2-1.8.9-slfo.1.1_2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="libip6tc2-1.8.9-slfo.1.1_2.1">
      <FullProductName ProductID="libip6tc2-1.8.9-slfo.1.1_2.1">libip6tc2-1.8.9-slfo.1.1_2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="libxtables12-1.8.9-slfo.1.1_2.1">
      <FullProductName ProductID="libxtables12-1.8.9-slfo.1.1_2.1">libxtables12-1.8.9-slfo.1.1_2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="libzypp-17.35.16-slfo.1.1_1.1">
      <FullProductName ProductID="libzypp-17.35.16-slfo.1.1_1.1">libzypp-17.35.16-slfo.1.1_1.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="python311-requests-2.32.3-slfo.1.1_2.1">
      <FullProductName ProductID="python311-requests-2.32.3-slfo.1.1_2.1">python311-requests-2.32.3-slfo.1.1_2.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="rsync-3.3.0-slfo.1.1_3.1">
      <FullProductName ProductID="rsync-3.3.0-slfo.1.1_3.1">rsync-3.3.0-slfo.1.1_3.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="xtables-plugins-1.8.9-slfo.1.1_2.1">
      <FullProductName ProductID="xtables-plugins-1.8.9-slfo.1.1_2.1">xtables-plugins-1.8.9-slfo.1.1_2.1</FullProductName>
    </Branch>
    <Relationship ProductReference="SL-Micro-release-6.1-slfo.1.11.2" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:SL-Micro-release-6.1-slfo.1.11.2">SL-Micro-release-6.1-slfo.1.11.2 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="iptables-1.8.9-slfo.1.1_2.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:iptables-1.8.9-slfo.1.1_2.1">iptables-1.8.9-slfo.1.1_2.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="kernel-default-6.4.0-24.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:kernel-default-6.4.0-24.1">kernel-default-6.4.0-24.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="libip4tc2-1.8.9-slfo.1.1_2.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:libip4tc2-1.8.9-slfo.1.1_2.1">libip4tc2-1.8.9-slfo.1.1_2.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="libip6tc2-1.8.9-slfo.1.1_2.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:libip6tc2-1.8.9-slfo.1.1_2.1">libip6tc2-1.8.9-slfo.1.1_2.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="libxtables12-1.8.9-slfo.1.1_2.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:libxtables12-1.8.9-slfo.1.1_2.1">libxtables12-1.8.9-slfo.1.1_2.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="libzypp-17.35.16-slfo.1.1_1.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:libzypp-17.35.16-slfo.1.1_1.1">libzypp-17.35.16-slfo.1.1_1.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="python311-requests-2.32.3-slfo.1.1_2.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:python311-requests-2.32.3-slfo.1.1_2.1">python311-requests-2.32.3-slfo.1.1_2.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="rsync-3.3.0-slfo.1.1_3.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:rsync-3.3.0-slfo.1.1_3.1">rsync-3.3.0-slfo.1.1_3.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</FullProductName>
    </Relationship>
    <Relationship ProductReference="xtables-plugins-1.8.9-slfo.1.1_2.1" RelationType="Default Component Of" RelatesToProductReference="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64">
      <FullProductName ProductID="Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64:xtables-plugins-1.8.9-slfo.1.1_2.1">xtables-plugins-1.8.9-slfo.1.1_2.1 as a component of Public Cloud Image google/sle-micro-6-1-byos-v20250210-arm64</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">A heap-based buffer overflow flaw was found in the rsync daemon. This issue is due to improper handling of attacker-controlled checksum lengths (s2length) in the code. When MAX_DIGEST_LEN exceeds the fixed SUM_LENGTH (16 bytes), an attacker can write out of bounds in the sum2 buffer.</Note>
    </Notes>
    <CVE>CVE-2024-12084</CVE>
    <ProductStatuses>
      <Status Type="Fixed"/>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>critical</Description>
      </Threat>
    </Threats>
  </Vulnerability>
  <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">A flaw was found in rsync which could be triggered when rsync compares file checksums. This flaw allows an attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and uninitialized memory and leak one byte of uninitialized stack data at a time.</Note>
    </Notes>
    <CVE>CVE-2024-12085</CVE>
    <ProductStatuses>
      <Status Type="Fixed"/>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
  </Vulnerability>
  <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">A flaw was found in rsync. It could allow a server to enumerate the contents of an arbitrary file from the client's machine. This issue occurs when files are being copied from a client to a server. During this process, the rsync server will send checksums of local data to the client to compare with in order to determine what data needs to be sent to the server. By sending specially constructed checksum values for arbitrary files, an attacker may be able to reconstruct the data of those files byte-by-byte based on the responses from the client.</Note>
    </Notes>
    <CVE>CVE-2024-12086</CVE>
    <ProductStatuses>
      <Status Type="Fixed"/>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
  </Vulnerability>
  <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">A path traversal vulnerability exists in rsync. It stems from behavior enabled by the `--inc-recursive` option, a default-enabled option for many client options and can be enabled by the server even if not explicitly enabled by the client. When using the `--inc-recursive` option, a lack of proper symlink verification coupled with deduplication checks occurring on a per-file-list basis could allow a server to write files outside of the client's intended destination directory. A malicious server could write malicious files to arbitrary locations named after valid directories/paths on the client.</Note>
    </Notes>
    <CVE>CVE-2024-12087</CVE>
    <ProductStatuses>
      <Status Type="Fixed"/>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>important</Description>
      </Threat>
    </Threats>
  </Vulnerability>
  <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">A flaw was found in rsync. When using the `--safe-links` option, the rsync client fails to properly verify if a symbolic link destination sent from the server contains another symbolic link within it. This results in a path traversal vulnerability, which may lead to arbitrary file write outside the desired directory.</Note>
    </Notes>
    <CVE>CVE-2024-12088</CVE>
    <ProductStatuses>
      <Status Type="Fixed"/>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
  </Vulnerability>
  <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">A flaw was found in rsync. This vulnerability arises from a race condition during rsync's handling of symbolic links. Rsync's default behavior when encountering symbolic links is to skip them. If an attacker replaced a regular file with a symbolic link at the right time, it was possible to bypass the default behavior and traverse symbolic links. Depending on the privileges of the rsync process, an attacker could leak sensitive information, potentially leading to privilege escalation.</Note>
    </Notes>
    <CVE>CVE-2024-12747</CVE>
    <ProductStatuses>
      <Status Type="Fixed"/>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
  </Vulnerability>
</cvrfdoc>
