<?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-47952</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-47952</ID>
    </Identification>
    <Status>Interim</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>2</Number>
        <Date>2023-05-15T23:16:58Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2023-01-03T00:41:36Z</InitialReleaseDate>
    <CurrentReleaseDate>2023-05-15T23:16:58Z</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-47952</Note>
    <Note Title="Mitre CVE Description" Type="Description" Ordinal="2" xml:lang="en">lxc-user-nic in lxc through 5.0.1 is installed setuid root, and may allow local users to infer whether any file exists, even within a protected directory tree, because "Failed to open" often indicates that a file does not exist, whereas "does not refer to a network namespace path" often indicates that a file exists. NOTE: this is different from CVE-2018-6556 because the CVE-2018-6556 fix design was based on the premise that "we will report back to the user that the open() failed but the user has no way of knowing why it failed"; however, in many realistic cases, there are no plausible reasons for failing except that the file does not exist.</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 Linux Enterprise Server 11 SP3 for Teradata">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Server 11 SP3 for Teradata">
        <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP3 for Teradata" CPE="cpe:/o:suse:suse_sles_teradata:11:sp3">SUSE Linux Enterprise Server 11 SP3 for Teradata</FullProductName>
      </Branch>
    </Branch>
    <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="liblxc-devel-5.0.2-1.1">
      <FullProductName ProductID="liblxc-devel-5.0.2-1.1">liblxc-devel-5.0.2-1.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="liblxc1-5.0.2-1.1">
      <FullProductName ProductID="liblxc1-5.0.2-1.1">liblxc1-5.0.2-1.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="lxc">
      <FullProductName ProductID="lxc" CPE="cpe:2.3:a:linuxcontainers:lxc:*:*:*:*:*:*:*:*">lxc</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="lxc-5.0.2-1.1">
      <FullProductName ProductID="lxc-5.0.2-1.1" CPE="cpe:2.3:a:linuxcontainers:lxc:5.0.2:*:*:*:*:*:*:*">lxc-5.0.2-1.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="lxc-bash-completion-5.0.2-1.1">
      <FullProductName ProductID="lxc-bash-completion-5.0.2-1.1">lxc-bash-completion-5.0.2-1.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="lxc-ja-doc-5.0.2-1.1">
      <FullProductName ProductID="lxc-ja-doc-5.0.2-1.1">lxc-ja-doc-5.0.2-1.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="lxc-ko-doc-5.0.2-1.1">
      <FullProductName ProductID="lxc-ko-doc-5.0.2-1.1">lxc-ko-doc-5.0.2-1.1</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="pam_cgfs-5.0.2-1.1">
      <FullProductName ProductID="pam_cgfs-5.0.2-1.1">pam_cgfs-5.0.2-1.1</FullProductName>
    </Branch>
    <Relationship ProductReference="liblxc-devel-5.0.2-1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:liblxc-devel-5.0.2-1.1">liblxc-devel-5.0.2-1.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="liblxc1-5.0.2-1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:liblxc1-5.0.2-1.1">liblxc1-5.0.2-1.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="lxc-5.0.2-1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:lxc-5.0.2-1.1">lxc-5.0.2-1.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="lxc-bash-completion-5.0.2-1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:lxc-bash-completion-5.0.2-1.1">lxc-bash-completion-5.0.2-1.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="lxc-ja-doc-5.0.2-1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:lxc-ja-doc-5.0.2-1.1">lxc-ja-doc-5.0.2-1.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="lxc-ko-doc-5.0.2-1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:lxc-ko-doc-5.0.2-1.1">lxc-ko-doc-5.0.2-1.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="pam_cgfs-5.0.2-1.1" RelationType="Default Component Of" RelatesToProductReference="openSUSE Tumbleweed">
      <FullProductName ProductID="openSUSE Tumbleweed:pam_cgfs-5.0.2-1.1">pam_cgfs-5.0.2-1.1 as a component of openSUSE Tumbleweed</FullProductName>
    </Relationship>
    <Relationship ProductReference="lxc" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 11 SP3 for Teradata">
      <FullProductName ProductID="SUSE Linux Enterprise Server 11 SP3 for Teradata:lxc">lxc as a component of SUSE Linux Enterprise Server 11 SP3 for Teradata</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">lxc-user-nic in lxc through 5.0.1 is installed setuid root, and may allow local users to infer whether any file exists, even within a protected directory tree, because "Failed to open" often indicates that a file does not exist, whereas "does not refer to a network namespace path" often indicates that a file exists. NOTE: this is different from CVE-2018-6556 because the CVE-2018-6556 fix design was based on the premise that "we will report back to the user that the open() failed but the user has no way of knowing why it failed"; however, in many realistic cases, there are no plausible reasons for failing except that the file does not exist.</Note>
    </Notes>
    <CVE>CVE-2022-47952</CVE>
    <ProductStatuses>
      <Status Type="Fixed">
        <ProductID>openSUSE Tumbleweed:liblxc-devel-5.0.2-1.1</ProductID>
        <ProductID>openSUSE Tumbleweed:liblxc1-5.0.2-1.1</ProductID>
        <ProductID>openSUSE Tumbleweed:lxc-5.0.2-1.1</ProductID>
        <ProductID>openSUSE Tumbleweed:lxc-bash-completion-5.0.2-1.1</ProductID>
        <ProductID>openSUSE Tumbleweed:lxc-ja-doc-5.0.2-1.1</ProductID>
        <ProductID>openSUSE Tumbleweed:lxc-ko-doc-5.0.2-1.1</ProductID>
        <ProductID>openSUSE Tumbleweed:pam_cgfs-5.0.2-1.1</ProductID>
      </Status>
      <Status Type="Known Not Affected">
        <ProductID>SUSE Linux Enterprise Server 11 SP3 for Teradata:lxc</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSetV3>
        <BaseScoreV3>6.3</BaseScoreV3>
        <VectorV3>CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N</VectorV3>
      </ScoreSetV3>
    </CVSSScoreSets>
  </Vulnerability>
</cvrfdoc>
