<?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 mod_auth_openidc is now available for HCE 3.0</DocumentTitle>
    <DocumentType>Security Advisory</DocumentType>
    <DocumentPublisher Type="Vendor">
      <ContactDetails>hws_security@huawei.com</ContactDetails>
      <IssuingAuthority>Huawei Cloud</IssuingAuthority>
    </DocumentPublisher>
    <DocumentTracking>
      <Identification>
        <ID>HCE3-SA-2025-0100</ID>
      </Identification>
      <Status>Final</Status>
      <Version>1.0</Version>
      <RevisionHistory>
        <Revision>
          <Number>1.0</Number>
          <Date>2025-10-09T06:38:18:00Z</Date>
          <Description>current version</Description>
        </Revision>
      </RevisionHistory>
      <InitialReleaseDate>2025-10-09T06:38:18:00Z</InitialReleaseDate>
      <CurrentReleaseDate>2025-10-09T06:38:18:00Z</CurrentReleaseDate>
      <Generator>
        <Engine>HCE SA Engine 1.0.0</Engine>
      </Generator>
    </DocumentTracking>
    <DocumentNotes>
      <Note Type="Summary" Ordinal="001">An update for mod_auth_openidc is now available for HCE 3.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):

mod_auth_openidc is an OpenID Certified authentication and authorization module for the Apache 2.x HTTP server that implements the OpenID Connect Relying Party functionality. Prior to 2.4.16.11, a bug in a mod_auth_openidc results in disclosure of protected content to unauthenticated users. The conditions for disclosure are an OIDCProviderAuthRequestMethod POST, a valid account, and there mustn_x27;t be any application-level gateway (or load balancer etc) protecting the server. When you request a protected resource, the response includes the HTTP status, the HTTP headers, the intended response (the self-submitting form), and the protected resource (with no headers). This is an example of a request for a protected resource, including all the data returned. In the case where mod_auth_openidc returns a form, it has to return OK from check_userid so as not to go down the error path in httpd. This means httpd will try to issue the protected resource. oidc_content_handler is called early, which has the opportunity to prevent the normal output being issued by httpd. oidc_content_handler has a number of checks for when it intervenes, but it doesn_x27;t check for this case, so the handler returns DECLINED. Consequently, httpd appends the protected content to the response. The issue has been patched in mod_auth_openidc versions &gt;= 2.4.16.11. (CVE-2025-31492)
</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="3.0">
            <FullProductName ProductID="HCE 3.0" CPE="cpe:/o:huawei:HCE:3.0">Huawei Cloud EulerOS 3.0</FullProductName>
          </Branch>
        </Branch>
      </Branch>
      <Branch Type="Product Version" Name="mod_auth_openidc">
        <FullProductName ProductID="mod_auth_openidc" CPE="cpe:/o:huawei:HCE:3.0">mod_auth_openidc</FullProductName>
      </Branch>
      <Relationship ProductReference="mod_auth_openidc" RelationType="Default Component Of" RelatesToProductReference="HCE 3.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-2025-31492</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2025-31492</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 3.0:mod_auth_openidc-2.4.16.11-1.hce3</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-31492</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>7.5</BaseScore>
          <Vector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N</Vector>
        </ScoreSet>
      </CVSSScoreSets>
      <Remediations/>
    </Vulnerability>
  </cvrfdoc>
