gsd-2023-41890
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
Sustainsys.Saml2 library adds SAML2P support to ASP.NET web sites, allowing the web site to act as a SAML2 Service Provider.
Prior to versions 1.0.3 and 2.9.2, when a response is processed, the issuer of the Identity Provider is not sufficiently validated. This could allow a malicious identity provider to craft a Saml2 response that is processed as if issued by another identity provider. It is also possible for a malicious end user to cause stored state intended for one identity provider to be used when processing the response from another provider. An application is impacted if they rely on any of these features in their authentication/authorization logic: the issuer of the generated identity and claims; or items in the stored request state (AuthenticationProperties). This issue is patched in versions 2.9.2 and 1.0.3. The `AcsCommandResultCreated` notification can be used to add the validation required if an upgrade to patched packages is not possible.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2023-41890", "id": "GSD-2023-41890" }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2023-41890" ], "details": "Sustainsys.Saml2 library adds SAML2P support to ASP.NET web sites, allowing the web site to act as a SAML2 Service Provider. \nPrior to versions 1.0.3 and 2.9.2, when a response is processed, the issuer of the Identity Provider is not sufficiently validated. This could allow a malicious identity provider to craft a Saml2 response that is processed as if issued by another identity provider. It is also possible for a malicious end user to cause stored state intended for one identity provider to be used when processing the response from another provider. An application is impacted if they rely on any of these features in their authentication/authorization logic: the issuer of the generated identity and claims; or items in the stored request state (AuthenticationProperties). This issue is patched in versions 2.9.2 and 1.0.3. The `AcsCommandResultCreated` notification can be used to add the validation required if an upgrade to patched packages is not possible.", "id": "GSD-2023-41890", "modified": "2023-12-13T01:20:45.453342Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2023-41890", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "Saml2", "version": { "version_data": [ { "version_affected": "=", "version_value": "\u003c 1.0.3" }, { "version_affected": "=", "version_value": "\u003e= 2.0.0, \u003c 2.9.2" } ] } } ] }, "vendor_name": "Sustainsys" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "Sustainsys.Saml2 library adds SAML2P support to ASP.NET web sites, allowing the web site to act as a SAML2 Service Provider. \nPrior to versions 1.0.3 and 2.9.2, when a response is processed, the issuer of the Identity Provider is not sufficiently validated. This could allow a malicious identity provider to craft a Saml2 response that is processed as if issued by another identity provider. It is also possible for a malicious end user to cause stored state intended for one identity provider to be used when processing the response from another provider. An application is impacted if they rely on any of these features in their authentication/authorization logic: the issuer of the generated identity and claims; or items in the stored request state (AuthenticationProperties). This issue is patched in versions 2.9.2 and 1.0.3. The `AcsCommandResultCreated` notification can be used to add the validation required if an upgrade to patched packages is not possible." } ] }, "impact": { "cvss": [ { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1" } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "cweId": "CWE-289", "lang": "eng", "value": "CWE-289: Authentication Bypass by Alternate Name" } ] }, { "description": [ { "cweId": "CWE-294", "lang": "eng", "value": "CWE-294: Authentication Bypass by Capture-replay" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/Sustainsys/Saml2/security/advisories/GHSA-fv2h-753j-9g39", "refsource": "MISC", "url": "https://github.com/Sustainsys/Saml2/security/advisories/GHSA-fv2h-753j-9g39" }, { "name": "https://github.com/Sustainsys/Saml2/issues/712", "refsource": "MISC", "url": "https://github.com/Sustainsys/Saml2/issues/712" }, { "name": "https://github.com/Sustainsys/Saml2/issues/713", "refsource": "MISC", "url": "https://github.com/Sustainsys/Saml2/issues/713" } ] }, "source": { "advisory": "GHSA-fv2h-753j-9g39", "discovery": "UNKNOWN" } }, "nvd.nist.gov": { "cve": { "configurations": [ { "nodes": [ { "cpeMatch": [ { "criteria": "cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:*", "matchCriteriaId": "1368FC9F-A8F8-490B-BE77-B898DFF61C5F", "versionEndExcluding": "1.0.3", "vulnerable": true }, { "criteria": "cpe:2.3:a:sustainsys:saml2:*:*:*:*:*:*:*:*", "matchCriteriaId": "1E4A2BA7-F6D7-4E13-AA65-EAD3393106B4", "versionEndExcluding": "2.9.2", "versionStartIncluding": "2.0.0", "vulnerable": true } ], "negate": false, "operator": "OR" } ] } ], "descriptions": [ { "lang": "en", "value": "Sustainsys.Saml2 library adds SAML2P support to ASP.NET web sites, allowing the web site to act as a SAML2 Service Provider. \nPrior to versions 1.0.3 and 2.9.2, when a response is processed, the issuer of the Identity Provider is not sufficiently validated. This could allow a malicious identity provider to craft a Saml2 response that is processed as if issued by another identity provider. It is also possible for a malicious end user to cause stored state intended for one identity provider to be used when processing the response from another provider. An application is impacted if they rely on any of these features in their authentication/authorization logic: the issuer of the generated identity and claims; or items in the stored request state (AuthenticationProperties). This issue is patched in versions 2.9.2 and 1.0.3. The `AcsCommandResultCreated` notification can be used to add the validation required if an upgrade to patched packages is not possible." }, { "lang": "es", "value": "La librer\u00eda Sustainsys.Saml2 agrega soporte SAML2P a los sitios web ASP.NET, lo que permite que el sitio web act\u00fae como un Proveedor de Servicios SAML2. Antes de las versiones 1.0.3 y 2.9.2, cuando se procesa una respuesta, el emisor del Proveedor de Identidad no est\u00e1 suficientemente validado. Esto podr\u00eda permitir que un proveedor de identidad malicioso cree una respuesta Saml2 que se procese como si fuera emitida por otro proveedor de identidad. Tambi\u00e9n es posible que un usuario final maliciso haga que se utilice el estado almacenado destinado a un proveedor de identidad al procesar la respuesta de otro proveedor. Una aplicaci\u00f3n se ve afectada si depende de cualquiera de estas caracter\u00edsticas en su l\u00f3gica de autenticaci\u00f3n/autorizaci\u00f3n: el emisor de la identidad y los reclamos generados; o elementos en el estado de solicitud almacenado (AuthenticationProperties). Este problema se solucion\u00f3 en las versiones 2.9.2 y 1.0.3. La notificaci\u00f3n `AcsCommandResultCreated` se puede utilizar para agregar la validaci\u00f3n requerida si no es posible actualizar los paquetes parcheados." } ], "id": "CVE-2023-41890", "lastModified": "2023-12-19T15:16:11.310", "metrics": { "cvssMetricV31": [ { "cvssData": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1" }, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary" }, { "cvssData": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1" }, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "security-advisories@github.com", "type": "Secondary" } ] }, "published": "2023-09-19T15:15:52.863", "references": [ { "source": "security-advisories@github.com", "tags": [ "Issue Tracking", "Patch" ], "url": "https://github.com/Sustainsys/Saml2/issues/712" }, { "source": "security-advisories@github.com", "tags": [ "Issue Tracking", "Patch" ], "url": "https://github.com/Sustainsys/Saml2/issues/713" }, { "source": "security-advisories@github.com", "tags": [ "Third Party Advisory" ], "url": "https://github.com/Sustainsys/Saml2/security/advisories/GHSA-fv2h-753j-9g39" } ], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [ { "description": [ { "lang": "en", "value": "CWE-289" }, { "lang": "en", "value": "CWE-294" } ], "source": "security-advisories@github.com", "type": "Primary" } ] } } } }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.