<?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>An update for shim is now available for HCE 2.0</DocumentTitle>
    <DocumentType>Security Advisory</DocumentType>
    <DocumentPublisher Type="Vendor">
      <ContactDetails>hws_security@huawei.com</ContactDetails>
      <IssuingAuthority>Huawei Cloud</IssuingAuthority>
    </DocumentPublisher>
    <DocumentTracking>
      <Identification>
        <ID>HCE2-SA-2023-0333</ID>
      </Identification>
      <Status>Final</Status>
      <Version>1.0</Version>
      <RevisionHistory>
        <Revision>
          <Number>1.0</Number>
          <Date>2023-11-28T10:32:39:00Z</Date>
          <Description>current version</Description>
        </Revision>
      </RevisionHistory>
      <InitialReleaseDate>2023-11-28T10:32:39:00Z</InitialReleaseDate>
      <CurrentReleaseDate>2023-11-28T10:32:39:00Z</CurrentReleaseDate>
      <Generator>
        <Engine>HCE SA Engine 1.0.0</Engine>
      </Generator>
    </DocumentTracking>
    <DocumentNotes>
      <Note Type="Summary" Ordinal="001">An update for shim is now available for HCE 2.0

HCE Security has rated this update as having a security impact of Moderate.A Common Vunlnerability Scoring System(CVSS)base score, which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section.</Note>
      <Note Type="General" Ordinal="002">Security Fix(es):

A vulnerability classified as critical has been found in rhboot shim up to 15.7 on ARM. This affects the function mirror_one_esl of the file mok.c of the component mok. Applying the patch 66e6579dbf921152f647a0c16da1d3b2f40861ca is able to eliminate this problem. The bugfix is ready for download at github.com. (CVE-2023-40546)

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex()
or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long
delays. Where the key or parameters that are being checked have been obtained
from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those
checks confirms that the modulus ('p' parameter) is not too large. Trying to use
a very large modulus is slow and OpenSSL will not normally use a modulus which
is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters
that have been supplied. Some of those checks use the supplied modulus value
even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained
from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions.
An application calling any of those other functions may similarly be affected.
The other functions affected by this are DH_check_ex() and
EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications
when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. (CVE-2023-3446)

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex()
or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long
delays. Where the key or parameters that are being checked have been obtained
from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing
CVE-2023-3446 it was discovered that a large q parameter value can also trigger
an overly long computation during some of these checks. A correct q value,
if present, cannot be larger than the modulus p parameter, thus it is
unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained
from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions.
An application calling any of those other functions may similarly be affected.
The other functions affected by this are DH_check_ex() and
EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications
when using the &quot;-check&quot; option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue. (CVE-2023-3817)
</Note>
      <Note Type="Legal Disclaimer" Ordinal="003">This document is provided on an &quot;AS IS&quot; basis and does not implyany kind of guarantee or warranty, either express or implied, including the warranties of merchantability or fitness for a particular purpose. In no eventshall Huawei or any of its directly or indirectly controlled subsidiaries or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages. Your use of the document, by any means, is totally at your own risk. Huawei is entitled to amend or update this document from time to time.
The information and data embodied in this document and any attachment are strictly confidential information of Huawei and are supplied on the understanding that they will be held confidentially and not disclosed to third parties without the prior written consent of Huawei. Use all reasonable efforts to protect the confidentiality of information. In particular, do not directly or indirectly disclose, allow access to, transmit or transfer information to a third party without our prior written consent. Thank you for your co-operation. Receipt of this security advisory shall be deemed as your consent of the terms and conditions above.</Note>
    </DocumentNotes>
    <DocumentReferences/>
    <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
      <Branch Type="Vendor" Name="HuaweiCloud">
        <Branch Type="Product Name" Name="HCE">
          <Branch Type="Product Version" Name="2.0">
            <FullProductName ProductID="HCE 2.0" CPE="cpe:/o:huawei:HCE:2.0">Huawei Cloud EulerOS 2.0</FullProductName>
          </Branch>
        </Branch>
      </Branch>
      <Branch Type="Product Version" Name="shim">
        <FullProductName ProductID="shim" CPE="cpe:/o:huawei:HCE:2.0">shim</FullProductName>
      </Branch>
      <Relationship ProductReference="shim" RelationType="Default Component Of" RelatesToProductReference="HCE 2.0"/>
    </ProductTree>
    <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="001">
      <Notes>
        <Note Type="Details" Ordinal="001">This vulnerability can be exploited only when the following conditions are present:
None Vulnerability details: For technical details, customers are advised to reference the website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40546</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2023-40546</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:shim-15.4-2.r22.hce2</ProductID>
        </Status>
      </ProductStatuses>
      <Threats>
        <Threat Type="Impact">
          <Description>For technical details, customers are advised to referencethe website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40546</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>5.5</BaseScore>
          <Vector>CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L</Vector>
        </ScoreSet>
      </CVSSScoreSets>
      <Remediations/>
    </Vulnerability>
    <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="002">
      <Notes>
        <Note Type="Details" Ordinal="001">This vulnerability can be exploited only when the following conditions are present:
None Vulnerability details: For technical details, customers are advised to reference the website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3446</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2023-3446</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:shim-15.4-2.r22.hce2</ProductID>
        </Status>
      </ProductStatuses>
      <Threats>
        <Threat Type="Impact">
          <Description>For technical details, customers are advised to referencethe website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3446</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>5.3</BaseScore>
          <Vector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L</Vector>
        </ScoreSet>
      </CVSSScoreSets>
      <Remediations/>
    </Vulnerability>
    <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="003">
      <Notes>
        <Note Type="Details" Ordinal="001">This vulnerability can be exploited only when the following conditions are present:
None Vulnerability details: For technical details, customers are advised to reference the website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3817</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2023-3817</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:shim-15.4-2.r22.hce2</ProductID>
        </Status>
      </ProductStatuses>
      <Threats>
        <Threat Type="Impact">
          <Description>For technical details, customers are advised to referencethe website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3817</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>5.3</BaseScore>
          <Vector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L</Vector>
        </ScoreSet>
      </CVSSScoreSets>
      <Remediations/>
    </Vulnerability>
  </cvrfdoc>
