CVE-2022-21671

{"id": "CVE-2022-21671", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 4.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N", "authentication": "SINGLE", "integrityImpact": "NONE", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.8}, {"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-01-11T15:15:08.640", "references": [{"url": "https://github.com/replit/crosis/commit/e44b6a8f5fa28cb2872e3c19bb8a205bb5bfc281", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/replit/crosis/security/advisories/GHSA-7w54-gp8x-f33m", "tags": ["Mitigation", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/replit/crosis/commit/e44b6a8f5fa28cb2872e3c19bb8a205bb5bfc281", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/replit/crosis/security/advisories/GHSA-7w54-gp8x-f33m", "tags": ["Mitigation", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-200"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}], "descriptions": [{"lang": "en", "value": "@replit/crosis is a JavaScript client that speaks Replit's container protocol. A vulnerability that involves exposure of sensitive information exists in versions prior to 7.3.1. When using this library as a way to programmatically communicate with Replit in a standalone fashion, if there are multiple failed attempts to contact Replit through a WebSocket, the library will attempt to communicate using a fallback poll-based proxy. The URL of the proxy has changed, so any communication done to the previous URL could potentially reach a server that is outside of Replit's control and the token used to connect to the Repl could be obtained by an attacker, leading to full compromise of that Repl (not of the account). This was patched in version 7.3.1 by updating the address of the fallback WebSocket polling proxy to the new one. As a workaround, a user may specify the new address for the polling host (`gp-v2.replit.com`) in the `ConnectArgs`. More information about this workaround is available in the GitHub Security Advisory."}, {"lang": "es", "value": "replit/crosis es un cliente JavaScript que habla el protocolo de contenedores de Replit. En versiones anteriores a la 7.3.1, se presenta una vulnerabilidad que implica la exposici\u00f3n de informaci\u00f3n confidencial. Cuando es usada esta biblioteca como una forma de comunicarse program\u00e1ticamente con Replit de forma independiente, si son presentados varios intentos fallidos de contactar con Replit mediante un WebSocket, la biblioteca intentar\u00e1 comunicarse usando un proxy basado en sondeo. La URL del proxy ha cambiado, por lo que cualquier comunicaci\u00f3n realizada a la URL anterior podr\u00eda potencialmente llegar a un servidor que est\u00e1 fuera del control de Replit y el token usado para conectarse al Repl podr\u00eda ser obtenido por un atacante, conllevando a un compromiso total de ese Repl (no de la cuenta). Esto fue parcheado en la versi\u00f3n 7.3.1 actualizando la direcci\u00f3n del proxy de sondeo WebSocket fallback a la nueva. Como soluci\u00f3n, el usuario puede especificar la nueva direcci\u00f3n del host de sondeo (\"gp-v2.replit.com\") en los \"ConnectArgs\". Se presenta m\u00e1s informaci\u00f3n sobre esta medida de mitigaci\u00f3n en el aviso de seguridad de GitHub"}], "lastModified": "2024-11-21T06:45:11.993", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:replit:crosis:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4AA2E7E2-9774-4EE0-8FA8-9A17E3A3D94D", "versionEndExcluding": "7.3.1"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}