<?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-2020-10134</DocumentTitle>
  <DocumentType>SUSE CVE</DocumentType>
  <DocumentPublisher Type="Vendor">
    <ContactDetails>security@suse.de</ContactDetails>
    <IssuingAuthority>SUSE Security Team</IssuingAuthority>
  </DocumentPublisher>
  <DocumentTracking>
    <Identification>
      <ID>SUSE CVE-2020-10134</ID>
    </Identification>
    <Status>Interim</Status>
    <Version>1</Version>
    <RevisionHistory>
      <Revision>
        <Number>15</Number>
        <Date>2023-02-13T01:10:09Z</Date>
        <Description>current</Description>
      </Revision>
    </RevisionHistory>
    <InitialReleaseDate>2022-04-19T15:34:07Z</InitialReleaseDate>
    <CurrentReleaseDate>2023-02-13T01:10:09Z</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-2020-10134</Note>
    <Note Title="Mitre CVE Description" Type="Description" Ordinal="2" xml:lang="en">Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when the unauthenticated user initiates different pairing methods in each peer device and an end-user erroneously completes both pairing procedures with the MITM using the confirmation number of one peer as the passkey of the other. An adjacent, unauthenticated attacker could be able to initiate any Bluetooth operation on either attacked device exposed by the enabled Bluetooth profiles. This exposure may be limited when the user must authorize certain access explicitly, but so long as a user assumes that it is the intended remote device requesting permissions, device-local protections may be weakened.</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 High Performance Computing 12 SP4">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise High Performance Computing 12 SP4">
        <FullProductName ProductID="SUSE Linux Enterprise High Performance Computing 12 SP4" CPE="cpe:/o:suse:sle-hpc:12:sp4">SUSE Linux Enterprise High Performance Computing 12 SP4</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Family" Name="SUSE Linux Enterprise Server 12 SP4">
      <Branch Type="Product Name" Name="SUSE Linux Enterprise Server 12 SP4">
        <FullProductName ProductID="SUSE Linux Enterprise Server 12 SP4" CPE="cpe:/o:suse:sles:12:sp4">SUSE Linux Enterprise Server 12 SP4</FullProductName>
      </Branch>
    </Branch>
    <Branch Type="Product Version" Name="bluez">
      <FullProductName ProductID="bluez" CPE="cpe:2.3:a:bluez:bluez:*:*:*:*:*:*:*:*">bluez</FullProductName>
    </Branch>
    <Branch Type="Product Version" Name="libbluetooth3">
      <FullProductName ProductID="libbluetooth3">libbluetooth3</FullProductName>
    </Branch>
    <Relationship ProductReference="bluez" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise High Performance Computing 12 SP4">
      <FullProductName ProductID="SUSE Linux Enterprise High Performance Computing 12 SP4:bluez">bluez as a component of SUSE Linux Enterprise High Performance Computing 12 SP4</FullProductName>
    </Relationship>
    <Relationship ProductReference="bluez" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 12 SP4">
      <FullProductName ProductID="SUSE Linux Enterprise Server 12 SP4:bluez">bluez as a component of SUSE Linux Enterprise Server 12 SP4</FullProductName>
    </Relationship>
    <Relationship ProductReference="libbluetooth3" RelationType="Default Component Of" RelatesToProductReference="SUSE Linux Enterprise Server 12 SP4">
      <FullProductName ProductID="SUSE Linux Enterprise Server 12 SP4:libbluetooth3">libbluetooth3 as a component of SUSE Linux Enterprise Server 12 SP4</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">Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when the unauthenticated user initiates different pairing methods in each peer device and an end-user erroneously completes both pairing procedures with the MITM using the confirmation number of one peer as the passkey of the other. An adjacent, unauthenticated attacker could be able to initiate any Bluetooth operation on either attacked device exposed by the enabled Bluetooth profiles. This exposure may be limited when the user must authorize certain access explicitly, but so long as a user assumes that it is the intended remote device requesting permissions, device-local protections may be weakened.</Note>
    </Notes>
    <CVE>CVE-2020-10134</CVE>
    <ProductStatuses>
      <Status Type="Known Affected">
        <ProductID>SUSE Linux Enterprise High Performance Computing 12 SP4:bluez</ProductID>
        <ProductID>SUSE Linux Enterprise Server 12 SP4:bluez</ProductID>
        <ProductID>SUSE Linux Enterprise Server 12 SP4:libbluetooth3</ProductID>
      </Status>
    </ProductStatuses>
    <Threats>
      <Threat Type="Impact">
        <Description>moderate</Description>
      </Threat>
    </Threats>
    <CVSSScoreSets>
      <ScoreSetV2>
        <BaseScoreV2>4.3</BaseScoreV2>
        <VectorV2>AV:A/AC:M/Au:N/C:P/I:P/A:N</VectorV2>
      </ScoreSetV2>
      <ScoreSetV3>
        <BaseScoreV3>5.9</BaseScoreV3>
        <VectorV3>CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:L</VectorV3>
      </ScoreSetV3>
    </CVSSScoreSets>
  </Vulnerability>
</cvrfdoc>
