CVE-2022-23600

{"id": "CVE-2022-23600", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 3.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:S/C:P/I:N/A:N", "authentication": "SINGLE", "integrityImpact": "NONE", "accessComplexity": "MEDIUM", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "LOW", "obtainAllPrivilege": false, "exploitabilityScore": 6.8, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 1.6}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "published": "2022-02-04T23:15:15.513", "references": [{"url": "https://github.com/fleetdm/fleet/commit/35d5a7b285f15ddd47486fa656e8b1acf3d48374", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/fleetdm/fleet/security/advisories/GHSA-ch68-7cf4-35vr", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/fleetdm/fleet/commit/35d5a7b285f15ddd47486fa656e8b1acf3d48374", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/fleetdm/fleet/security/advisories/GHSA-ch68-7cf4-35vr", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-287"}]}], "descriptions": [{"lang": "en", "value": "fleet is an open source device management, built on osquery. Versions prior to 4.9.1 expose a limited ability to spoof SAML authentication with missing audience verification. This impacts deployments using SAML SSO in two specific cases: 1. A malicious or compromised Service Provider (SP) could reuse the SAML response to log into Fleet as a user -- only if the user has an account with the same email in Fleet, _and_ the user signs into the malicious SP via SAML SSO from the same Identity Provider (IdP) configured with Fleet. 2. A user with an account in Fleet could reuse a SAML response intended for another SP to log into Fleet. This is only a concern if the user is blocked from Fleet in the IdP, but continues to have an account in Fleet. If the user is blocked from the IdP entirely, this cannot be exploited. Fleet 4.9.1 resolves this issue. Users unable to upgrade should: Reduce the length of sessions on your IdP to reduce the window for malicious re-use, Limit the amount of SAML Service Providers/Applications used by user accounts with access to Fleet, and When removing access to Fleet in the IdP, delete the Fleet user from Fleet as well."}, {"lang": "es", "value": "fleet es un administrador de dispositivos de c\u00f3digo abierto, construido sobre osquery. Las versiones anteriores a la 4.9.1 exponen una capacidad limitada para falsificar la autenticaci\u00f3n SAML con una falta de verificaci\u00f3n de audiencia. Esto afecta a los despliegues que usan SAML SSO en dos casos espec\u00edficos: 1. Un Proveedor de Servicios (SP) malicioso o comprometido podr\u00eda reusar la respuesta SAML para iniciar sesi\u00f3n en Fleet como un usuario - s\u00f3lo si el usuario presenta una cuenta con el mismo correo electr\u00f3nico en Fleet, _y_ el usuario es registrado en el SP malicioso por medio de SAML SSO desde el mismo Proveedor de Identidad (IdP) configurado con Fleet. 2. Un usuario con una cuenta en Fleet podr\u00eda reusar una respuesta SAML destinada a otro SP para iniciar sesi\u00f3n en Fleet. Esto s\u00f3lo es un problema si el usuario est\u00e1 bloqueado de Fleet en el IdP, pero sigue teniendo una cuenta en Fleet. Si el usuario est\u00e1 bloqueado en el IdP por completo, esto no puede ser explotado. Fleet versi\u00f3n 4.9.1 resuelve este problema. Los usuarios que no puedan actualizarse deber\u00e1n: Reducir la duraci\u00f3n de las sesiones en su IdP para reducir la ventana de re\u00faso maliciosa, Limitar la cantidad de Proveedores de Servicios SAML/Aplicaciones usadas por las cuentas de usuario con acceso a Fleet, y Cuando elimine el acceso a Fleet en el IdP, elimine tambi\u00e9n el usuario de Fleet de Fleet"}], "lastModified": "2024-11-21T06:48:54.237", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:fleetdm:fleet:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "15208DF4-45B8-401E-A63A-9073A80C8AF1", "versionEndExcluding": "4.9.1"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}