CVE-2025-31492

{"id": "CVE-2025-31492", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.2, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-04-06T20:15:15.063", "references": [{"url": "https://github.com/OpenIDC/mod_auth_openidc/commit/b59b8ad63411857090ba1088e23fe414c690c127", "source": "security-advisories@github.com"}, {"url": "https://github.com/OpenIDC/mod_auth_openidc/security/advisories/GHSA-59jp-rwph-878r", "source": "security-advisories@github.com"}, {"url": "https://lists.debian.org/debian-lts-announce/2025/04/msg00025.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-200"}]}], "descriptions": [{"lang": "en", "value": "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'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'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 >= 2.4.16.11."}, {"lang": "es", "value": "mod_auth_openidc es un m\u00f3dulo de autenticaci\u00f3n y autorizaci\u00f3n con certificaci\u00f3n OpenID para el servidor HTTP Apache 2.x que implementa la funcionalidad de usuario autenticado de OpenID Connect. Antes de la versi\u00f3n 2.4.16.11, un error en mod_auth_openidc provocaba la divulgaci\u00f3n de contenido protegido a usuarios no autenticados. Las condiciones para la divulgaci\u00f3n son un POST OIDCProviderAuthRequestMethod, una cuenta v\u00e1lida y que no haya ninguna puerta de enlace a nivel de aplicaci\u00f3n (ni balanceador de carga, etc.) protegiendo el servidor. Al solicitar un recurso protegido, la respuesta incluye el estado HTTP, los encabezados HTTP, la respuesta prevista (el formulario de autoenv\u00edo) y el recurso protegido (sin encabezados). Este es un ejemplo de una solicitud de un recurso protegido, incluyendo todos los datos devueltos. Si mod_auth_openidc devuelve un formulario, debe devolver \"OK\" de check_userid para evitar el error en httpd. Esto significa que httpd intentar\u00e1 emitir el recurso protegido. oidc_content_handler se llama antes, lo que puede impedir que httpd emita la salida normal. oidc_content_handler realiza varias comprobaciones cuando interviene, pero no verifica este caso, por lo que el controlador devuelve DECLINED. En consecuencia, httpd a\u00f1ade el contenido protegido a la respuesta. El problema se ha corregido en las versiones de mod_auth_openidc posteriores a la 2.4.16.11."}], "lastModified": "2025-04-17T11:15:48.567", "sourceIdentifier": "security-advisories@github.com"}