CVE-2021-37705

{"id": "CVE-2021-37705", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 6.8, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "MEDIUM", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.6, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 10.0, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.9}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 10.0, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.9}]}, "published": "2021-08-13T21:15:06.973", "references": [{"url": "https://github.com/microsoft/onefuzz/commit/2fcb4998887959b4fa11894a068d689189742cb1", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/onefuzz/pull/1153", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/onefuzz/releases/tag/2.31.0", "tags": ["Release Notes", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/onefuzz/security/advisories/GHSA-q5vh-6whw-x745", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://pypi.org/project/onefuzz/", "tags": ["Product"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-863"}]}, {"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-285"}, {"lang": "en", "value": "CWE-346"}]}], "descriptions": [{"lang": "en", "value": "OneFuzz is an open source self-hosted Fuzzing-As-A-Service platform. Starting with OneFuzz 2.12.0 or greater, an incomplete authorization check allows an authenticated user from any Azure Active Directory tenant to make authorized API calls to a vulnerable OneFuzz instance. To be vulnerable, a OneFuzz deployment must be both version 2.12.0 or greater and deployed with the non-default --multi_tenant_domain option. This can result in read/write access to private data such as software vulnerability and crash information, security testing tools and proprietary code and symbols. Via authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources. This issue is resolved starting in release 2.31.0, via the addition of application-level check of the bearer token's `issuer` against an administrator-configured allowlist. As a workaround users can restrict access to the tenant of a deployed OneFuzz instance < 2.31.0 by redeploying in the default configuration, which omits the `--multi_tenant_domain` option."}, {"lang": "es", "value": "OneFuzz es una plataforma de Fuzzing-As-A-Service de c\u00f3digo abierto. A partir de la versi\u00f3n 2.12.0 o superior de OneFuzz, una comprobaci\u00f3n de autorizaci\u00f3n incompleta permite a un usuario autenticado de cualquier inquilino de Azure Active Directory realizar llamadas de API autorizadas a una instancia vulnerable de OneFuzz. Para ser vulnerable, una implementaci\u00f3n de OneFuzz debe ser ambas versi\u00f3n 2.12.0 o superior y estar implementada con la opci\u00f3n no predeterminada --multi_tenant_domain. Esto puede resultar en un acceso de lectura y escritura a datos privados, como informaci\u00f3n sobre vulnerabilidades y bloqueo de software, herramientas de pruebas de seguridad y c\u00f3digo y s\u00edmbolos propios. Por medio de llamadas autorizadas a la API, esto tambi\u00e9n habilita la manipulaci\u00f3n de los datos existentes y una ejecuci\u00f3n no autorizada de c\u00f3digo en los recursos inform\u00e1ticos de Azure. Este problema es resuelto a partir de la versi\u00f3n 2.31.0, por medio de la adici\u00f3n de la comprobaci\u00f3n a nivel de aplicaci\u00f3n del \"issuer\" del token de portador con una lista de permisos configurada por el administrador. Como soluci\u00f3n, los usuarios pueden restringir el acceso al inquilino de una instancia de OneFuzz desplegada anterior a 2.31.0 al redesplegar en la configuraci\u00f3n predeterminada, que omite la opci\u00f3n \"--multi_tenant_domain\"."}], "lastModified": "2022-10-27T12:46:09.410", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:microsoft:onefuzz:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "8F3330CA-CBB6-4DDD-8D1B-54D3099C15EC", "versionEndExcluding": "2.31.0", "versionStartIncluding": "2.12.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}