<?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 golang 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-0284</ID>
      </Identification>
      <Status>Final</Status>
      <Version>1.0</Version>
      <RevisionHistory>
        <Revision>
          <Number>1.0</Number>
          <Date>2023-09-15T08:04:42:00Z</Date>
          <Description>current version</Description>
        </Revision>
      </RevisionHistory>
      <InitialReleaseDate>2023-09-15T08:04:42:00Z</InitialReleaseDate>
      <CurrentReleaseDate>2023-09-15T08:04:42:00Z</CurrentReleaseDate>
      <Generator>
        <Engine>HCE SA Engine 1.0.0</Engine>
      </Generator>
    </DocumentTracking>
    <DocumentNotes>
      <Note Type="Summary" Ordinal="001">An update for golang 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):

Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures. With fix, the size of RSA keys transmitted during handshakes is restricted to &lt;= 8192 bits. Based on a survey of publicly trusted RSA keys, there are currently only three certificates in circulation with keys larger than this, and all three appear to be test certificates that are not actively deployed. It is possible there are larger keys in use in private PKIs, but we target the web PKI, so causing breakage here in the interests of increasing the default safety of users of crypto/tls seems reasonable. (CVE-2023-29409)
</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="golang">
        <FullProductName ProductID="golang" CPE="cpe:/o:huawei:HCE:2.0">golang</FullProductName>
      </Branch>
      <Relationship ProductReference="golang" 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-29409</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2023-29409</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:golang-1.17.3-1.r24.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-29409</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>
