CVE-2021-21309

{"id": "CVE-2021-21309", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 6.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", "authentication": "SINGLE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 5.4, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 2.7, "exploitabilityScore": 2.2}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}]}, "published": "2021-02-26T22:15:19.457", "references": [{"url": "https://github.com/redis/redis/commit/c992857618db99776917f10bf4f2345a5fdc78b0", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/redis/redis/pull/8522", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/redis/redis/security/advisories/GHSA-hgj8-vff2-7cjf", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://security.gentoo.org/glsa/202103-02", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/redis/redis/commit/c992857618db99776917f10bf4f2345a5fdc78b0", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/redis/redis/pull/8522", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/redis/redis/security/advisories/GHSA-hgj8-vff2-7cjf", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security.gentoo.org/glsa/202103-02", "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-190"}]}], "descriptions": [{"lang": "en", "value": "Redis is an open-source, in-memory database that persists on disk. In affected versions of Redis an integer overflow bug in 32-bit Redis version 4.0 or newer could be exploited to corrupt the heap and potentially result with remote code execution. Redis 4.0 or newer uses a configurable limit for the maximum supported bulk input size. By default, it is 512MB which is a safe value for all platforms. If the limit is significantly increased, receiving a large request from a client may trigger several integer overflow scenarios, which would result with buffer overflow and heap corruption. We believe this could in certain conditions be exploited for remote code execution. By default, authenticated Redis users have access to all configuration parameters and can therefore use the \u201cCONFIG SET proto-max-bulk-len\u201d to change the safe default, making the system vulnerable. **This problem only affects 32-bit Redis (on a 32-bit system, or as a 32-bit executable running on a 64-bit system).** The problem is fixed in version 6.2, and the fix is back ported to 6.0.11 and 5.0.11. Make sure you use one of these versions if you are running 32-bit Redis. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent clients from directly executing `CONFIG SET`: Using Redis 6.0 or newer, ACL configuration can be used to block the command. Using older versions, the `rename-command` configuration directive can be used to rename the command to a random string unknown to users, rendering it inaccessible. Please note that this workaround may have an additional impact on users or operational systems that expect `CONFIG SET` to behave in certain ways."}, {"lang": "es", "value": "Redis es una base de datos en memoria de c\u00f3digo abierto que persiste en el disco. En las versiones afectadas de Redis, un error de desbordamiento de enteros en Redis de 32 bits versi\u00f3n 4.0 o m\u00e1s reciente podr\u00eda ser explotada para corromper la pila y potencialmente resultar en una ejecuci\u00f3n de c\u00f3digo remota. Redis versiones 4.0 o posteriores, usa un l\u00edmite configurable para el tama\u00f1o m\u00e1ximo de la entrada masiva admitida. Por defecto, es de 512 MB, que es un valor seguro para todas las plataformas. Si el l\u00edmite aumenta significativamente, recibir una petici\u00f3n grande de un cliente puede desencadenar varios escenarios de desbordamiento de enteros, que podr\u00eda resultar en un desbordamiento del b\u00fafer y una corrupci\u00f3n de la pila. Creemos que, en determinadas condiciones, esta podr\u00eda ser explotada para una ejecuci\u00f3n de c\u00f3digo remota. Por defecto, usuarios de Redis autenticados poseen acceso a todos los par\u00e1metros de configuraci\u00f3n y, por lo tanto, pueden usar \"CONFIG SET proto-max-bulk-len\" para cambiar el valor predeterminado seguro, haciendo que el sistema sea vulnerable.** Este problema solo afecta a Redis de 32 bits (en un sistema de 32 bits o como un ejecutable de 32 bits que se ejecuta en un sistema de 64 bits). ** El problema se corrigi\u00f3 en la versi\u00f3n 6.2 y la soluci\u00f3n se ha modificado a versiones 6.0.11 y 5.0.11. Aseg\u00farese de usar una de estas versiones si est\u00e1 ejecutando Redis de 32 bits. Una soluci\u00f3n alternativa para mitigar el problema sin parchear el ejecutable de redis-server es impedir que los clientes ejecuten directamente `CONFIG SET`: Con Redis versiones 6.0 o m\u00e1s recientes, la configuraci\u00f3n de ACL puede ser usada para bloquear el comando. Utilizando versiones anteriores, la directiva de configuraci\u00f3n \"rename-command\" puede ser usada para cambiar el nombre del comando a una cadena aleatoria desconocida para usuarios, haci\u00e9ndolo inaccesible. Tome en cuenta que esta soluci\u00f3n puede tener un impacto adicional en los usuarios o los sistemas operativos que esperan que \"CONFIG SET\" se comporte de determinadas formas"}], "lastModified": "2024-11-21T05:47:59.563", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:redislabs:redis:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "366C8910-66E7-4AB6-873C-70595AD42ADA", "versionEndExcluding": "5.0.11", "versionStartIncluding": "4.0"}, {"criteria": "cpe:2.3:a:redislabs:redis:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "C345BCBB-EB73-4DA5-93F0-42AB9E903CE5", "versionEndExcluding": "6.0.11", "versionStartIncluding": "6.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}