{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-05-01T16:44:18.854","vulnerabilities":[{"cve":{"id":"CVE-2025-24895","sourceIdentifier":"security-advisories@github.com","published":"2025-02-18T19:15:28.240","lastModified":"2026-04-15T00:35:42.020","vulnStatus":"Deferred","cveTags":[],"descriptions":[{"lang":"en","value":"CIE.AspNetCore.Authentication is an AspNetCore Remote Authenticator for CIE 3.0. Authentication using Spid and CIE is based on the SAML2 standard which provides two entities: 1. Identity Provider (IDP): the system that authenticates users and provides identity information (SAML affirmation) to the Service Provider, in essence, is responsible for the management of the credentials and identity of users; 2. Service Provider (SP): the system that provides a service to the user and relies on the Identity Provider to authenticate the user, receives SAML assertions from the IdP to grant access to resources. The library cie-aspnetcore refers to the second entity, the SP, and implements the validation logic of SAML assertions within SAML responses. In affected versions there is no guarantee that the first signature refers to the root object, it follows that if an attacker injects an item signed as the first element, all other signatures will not be verified. The only requirement is to have an XML element legitimately signed by the IdP, a condition that is easily met using the IdP's public metadata. An attacker could create an arbitrary SAML response that would be accepted by SPs using vulnerable SDKs, allowing him to impersonate any Spid and/or CIE user. This issue has been addressed in version 2.1.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability."},{"lang":"es","value":"CIE.AspNetCore.Authentication es un Autenticador Remoto AspNetCore para CIE 3.0. La autenticación mediante Spid y CIE se basa en el estándar SAML2 que proporciona dos entidades: 1. Proveedor de Identidad (IDP): el sistema que autentica a los usuarios y proporciona información de identidad (afirmación SAML) al Proveedor de Servicios, en esencia, es responsable de la gestión de las credenciales e identidad de los usuarios; 2. Proveedor de Servicios (SP): el sistema que proporciona un servicio al usuario y se basa en el Proveedor de Identidad para autenticar al usuario, recibe aserciones SAML del IdP para otorgar acceso a los recursos. La librería cie-aspnetcore hace referencia a la segunda entidad, el SP, e implementa la lógica de validación de aserciones SAML dentro de las respuestas SAML. En las versiones afectadas no hay garantía de que la primera firma se refiera al objeto raíz, se deduce que si un atacante inyecta un elemento firmado como primer elemento, todas las demás firmas no serán verificadas. El único requisito es tener un elemento XML firmado legítimamente por el IdP, una condición que se cumple fácilmente utilizando los metadatos públicos del IdP. Un atacante podría crear una respuesta SAML arbitraria que sería aceptada por los SP utilizando SDK vulnerables, lo que le permitiría hacerse pasar por cualquier usuario de Spid y/o CIE. Este problema se ha solucionado en la versión 2.1.0 y se recomienda a todos los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad."}],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":9.1,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":3.9,"impactScore":5.2}]},"weaknesses":[{"source":"security-advisories@github.com","type":"Secondary","description":[{"lang":"en","value":"CWE-287"}]}],"references":[{"url":"https://github.com/italia/cie-aspnetcore/security/advisories/GHSA-vq63-8f72-f486","source":"security-advisories@github.com"}]}}]}