<?xml version="1.0" encoding="UTF-8"?>
<cvrfdoc xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:cvrf="http://docs.oasis-open.org/csaf/ns/csaf-cvrf/v1.2/cvrf" xmlns:cvrf-common="http://docs.oasis-open.org/csaf/ns/csaf-cvrf/v1.2/common" xmlns:cvssv2="http://scap.nist.gov/schema/cvss-v2/1.0" xmlns:cvssv3="https://www.first.org/cvss/cvss-v3.0.xsd" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:ns0="http://purl.org/dc/elements/1.1/" xmlns:prod="http://docs.oasis-open.org/csaf/ns/csaf-cvrf/v1.2/prod" xmlns:scap-core="http://scap.nist.gov/schema/scap-core/1.0" xmlns:sch="http://purl.oclc.org/dsdl/schematron" xmlns:vuln="http://docs.oasis-open.org/csaf/ns/csaf-cvrf/v1.2/vuln" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://docs.oasis-open.org/csaf/ns/csaf-cvrf/v1.2/cvrf">
  <DocumentTitle xml:lang="en">CVE-2022-26612</DocumentTitle>
  <DocumentType>SUSE CVE</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE CVE-2022-26612</ID>
    </Identification>
    <Status>Interim</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>6</Number>
        <Date>2025-02-16T03:07:00Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2022-04-11T11:44:20Z</InitialReleaseDate>
    <CurrentReleaseDate>2025-02-16T03:07:00Z</CurrentReleaseDate>
    <Generator>
      <Engine>cve-database/bin/generate-cvrf-cve.pl</Engine>
      <Date>2020-12-27T01:00:00Z</Date>
    </Generator>
  </DocumentTracking>
  <DocumentNotes>
    <Note Title="CVE" Type="Summary" Ordinal="1" xml:lang="en">CVE-2022-26612</Note>
    <Note Title="Mitre CVE Description" Type="Description" Ordinal="2" xml:lang="en">In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 3.2.3</Note>
    <Note Title="Terms of Use" Type="Legal Disclaimer" Ordinal="4" 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://www.suse.com/support/security/rating/</URL>
      <Description>SUSE Security Ratings</Description>
    </Reference>
  </DocumentReferences>
  <ProductTree xmlns="http://docs.oasis-open.org/csaf/ns/csaf-cvrf/v1.2/prod">
    <Branch Type="Product Family" Name="SUSE Manager Server Module 4.1">
      <Branch Type="Product Name" Name="SUSE Manager Server Module 4.1">
        <FullProductName ProductID="SUSE Manager Server Module 4.1" CPE="cpe:/o:suse:sle-module-suse-manager-server:4.1">SUSE Manager Server Module 4.1</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Family" Name="SUSE Manager Server Module 4.2">
      <Branch Type="Product Name" Name="SUSE Manager Server Module 4.2">
        <FullProductName ProductID="SUSE Manager Server Module 4.2" CPE="cpe:/o:suse:sle-module-suse-manager-server:4.2">SUSE Manager Server Module 4.2</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Family" Name="SUSE Manager Server Module 4.3">
      <Branch Type="Product Name" Name="SUSE Manager Server Module 4.3">
        <FullProductName ProductID="SUSE Manager Server Module 4.3" CPE="cpe:/o:suse:sle-module-suse-manager-server:4.3">SUSE Manager Server Module 4.3</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="hadoop">
      <FullProductName ProductID="hadoop" CPE="cpe:2.3:a:apache:hadoop:*:*:*:*:*:*:*:*">hadoop</FullProductName>
    </Branch>
    <Relationship ProductReference="hadoop" RelationType="Default Component Of" RelatesToProductReference="SUSE Manager Server Module 4.1">
      <FullProductName ProductID="SUSE Manager Server Module 4.1:hadoop">hadoop as a component of SUSE Manager Server Module 4.1</FullProductName>
    </Relationship>
    <Relationship ProductReference="hadoop" RelationType="Default Component Of" RelatesToProductReference="SUSE Manager Server Module 4.2">
      <FullProductName ProductID="SUSE Manager Server Module 4.2:hadoop">hadoop as a component of SUSE Manager Server Module 4.2</FullProductName>
    </Relationship>
    <Relationship ProductReference="hadoop" RelationType="Default Component Of" RelatesToProductReference="SUSE Manager Server Module 4.3">
      <FullProductName ProductID="SUSE Manager Server Module 4.3:hadoop">hadoop as a component of SUSE Manager Server Module 4.3</FullProductName>
    </Relationship>
  </ProductTree>
  <Vulnerability xmlns="http://docs.oasis-open.org/csaf/ns/csaf-cvrf/v1.2/vuln" Ordinal="1">
    <Notes>
      <Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 3.2.3</Note>
    </Notes>
    <CVE>CVE-2022-26612</CVE>
    <ProductStatuses>
      <Status Type="Known Not Affected">
        <ProductID>SUSE Manager Server Module 4.1:hadoop</ProductID>
        <ProductID>SUSE Manager Server Module 4.2:hadoop</ProductID>
        <ProductID>SUSE Manager Server Module 4.3:hadoop</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>critical</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSetV2>
        <BaseScoreV2>7.5</BaseScoreV2>
        <VectorV2>AV:N/AC:L/Au:N/C:P/I:P/A:P</VectorV2>
      </ScoreSetV2>
      <ScoreSetV3>
        <BaseScoreV3>9.8</BaseScoreV3>
        <VectorV3>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H</VectorV3>
      </ScoreSetV3>
    </CVSSScoreSets>
  </Vulnerability>
</cvrfdoc>
