<?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 edk2 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-2025-0300</ID>
      </Identification>
      <Status>Final</Status>
      <Version>1.0</Version>
      <RevisionHistory>
        <Revision>
          <Number>1.0</Number>
          <Date>2025-12-09T06:53:37:00Z</Date>
          <Description>current version</Description>
        </Revision>
      </RevisionHistory>
      <InitialReleaseDate>2025-12-09T06:53:37:00Z</InitialReleaseDate>
      <CurrentReleaseDate>2025-12-09T06:53:37:00Z</CurrentReleaseDate>
      <Generator>
        <Engine>HCE SA Engine 1.0.0</Engine>
      </Generator>
    </DocumentTracking>
    <DocumentNotes>
      <Note Type="Summary" Ordinal="001">An update for edk2 is now available for HCE 2.0

HCE Security has rated this update as having a security impact of Important.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):

Issue summary: Generating excessively long X9.42 DH keys or checking
excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to
generate an X9.42 DH key may experience long delays.  Likewise, applications
that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check()
to check an X9.42 DH key or X9.42 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.

While DH_check() performs all the necessary checks (as of CVE-2023-3817),
DH_check_pub_key() doesn't make any of these checks, and is therefore
vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large
P, it doesn't check for an excessively large Q.

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

DH_generate_key() and DH_check_pub_key() are also 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_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the
&quot;-pubcheck&quot; option, as well as the OpenSSL genpkey command line application.

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-5678)

EDK2 contains a vulnerability in BIOS where an attacker may cause “Protection Mechanism Failure” by local access. Successful exploitation of this vulnerability will lead to arbitrary code execution and impact Confidentiality, Integrity, and Availability. (CVE-2025-3770)

Issue summary: An application trying to decrypt CMS messages encrypted using
password based encryption can trigger an out-of-bounds read and write.

Impact summary: This out-of-bounds read may trigger a crash which leads to
Denial of Service for an application. The out-of-bounds write can cause
a memory corruption which can have various consequences including
a Denial of Service or Execution of attacker-supplied code.

Although the consequences of a successful exploit of this vulnerability
could be severe, the probability that the attacker would be able to
perform it is low. Besides, password based (PWRI) encryption support in CMS
messages is very rarely used. For that reason the issue was assessed as
Moderate severity according to our Security Policy.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this
issue, as the CMS implementation is outside the OpenSSL FIPS module
boundary. (CVE-2025-9230)

EDK2 contains a vulnerability in BIOS where a user may cause an Integer Overflow or Wraparound by network means. A successful exploitation of this vulnerability may lead to denial of service. (CVE-2024-38805)
</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="edk2">
        <FullProductName ProductID="edk2" CPE="cpe:/o:huawei:HCE:2.0">edk2</FullProductName>
      </Branch>
      <Relationship ProductReference="edk2" 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-5678</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2023-5678</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:edk2-202011-25.r4.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-5678</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="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-2025-3770</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2025-3770</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:edk2-202011-25.r4.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-2025-3770</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>7.0</BaseScore>
          <Vector>CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H</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-2025-9230</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2025-9230</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:edk2-202011-25.r4.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-2025-9230</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>7.5</BaseScore>
          <Vector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</Vector>
        </ScoreSet>
      </CVSSScoreSets>
      <Remediations/>
    </Vulnerability>
    <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="004">
      <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-2024-38805</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2024-38805</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:edk2-202011-25.r4.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-2024-38805</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>6.3</BaseScore>
          <Vector>CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H</Vector>
        </ScoreSet>
      </CVSSScoreSets>
      <Remediations/>
    </Vulnerability>
  </cvrfdoc>
