CVE-2026-56388

{"id": "CVE-2026-56388", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-56388", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-10-30T13:57:39.892176Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"vendor": "Apache Software Foundation", "product": "Apache bRPC", "versions": [{"status": "affected", "version": "0", "lessThan": "1.18.0", "versionType": "semver"}], "packageURL": "pkg:github/apache/brpc", "packageName": "apache/brpc", "collectionURL": "https://github.com", "defaultStatus": "unaffected"}]}], "published": "2026-10-21T12:17:21.680", "references": [{"url": "https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb", "source": "security@apache.org"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-252"}, {"lang": "en", "value": "CWE-617"}, {"lang": "en", "value": "CWE-787"}]}], "descriptions": [{"lang": "en", "value": "The Redis server command parser in Apache bRPC accepts an empty RESP array as a command header. A remote unauthenticated attacker who can reach a bRPC server with Redis service enabled can send an empty array header followed by a bulk string, causing an out-of-bounds write in the parser and crashing the process.\n\nRoot Cause:\nRedisCommandParser::ConsumeImpl rejected negative RESP array counts but accepted zero. It resized the command argument vector to zero elements and continued parsing. When a following bulk string was parsed, the only index guard was a CHECK. In configurations where fatal logs do not abort immediately, execution could continue and write to _args[0] even though the vector was empty.\n\nAffected Scenarios:\nDeployments that enable ServerOptions.redis_service and accept Redis protocol traffic from untrusted clients. The issue is reached during parsing before command handling or authentication.\n\nHow to Fix:\n1. Upgrade bRPC to version 1.18.0, which fixes this issue.\n2. Apply this patch: https://github.com/apache/brpc/pull/3354 \n\nNote:\nThe fix rejects empty RESP arrays as invalid Redis commands and replaces the internal index CHECK with an explicit parse error so malformed command streams cannot fall through to an indexed vector write."}, {"lang": "es", "value": "El analizador de comandos del servidor Redis en Apache bRPC acepta un arreglo RESP vac\u00edo como encabezado de comando. Un atacante remoto no autenticado que pueda alcanzar un servidor bRPC con el servicio Redis habilitado puede enviar un encabezado de arreglo vac\u00edo seguido de una cadena bulk, provocando una escritura fuera de l\u00edmites en el analizador y el bloqueo del proceso.\\n\\nCausa ra\u00edz:\\nRedisCommandParser::ConsumeImpl rechaz\u00f3 recuentos de arreglos RESP negativos pero acept\u00f3 cero. Redimension\u00f3 el vector de argumentos del comando a cero elementos y continu\u00f3 el an\u00e1lisis. Cuando se analiz\u00f3 una cadena bulk posterior, la \u00fanica protecci\u00f3n de \u00edndice era un CHECK. En configuraciones donde los registros fatales no abortan inmediatamente, la ejecuci\u00f3n podr\u00eda continuar y escribir en _args[0] aunque el vector estuviera vac\u00edo.\\n\\nEscenarios afectados:\\nImplementaciones que habilitan ServerOptions.redis_service y aceptan tr\u00e1fico del protocolo Redis de clientes no confiables. El problema se alcanza durante el an\u00e1lisis antes del manejo del comando o la autenticaci\u00f3n.\\n\\nC\u00f3mo solucionar:\\n1. Actualizar bRPC a la versi\u00f3n 1.18.0, que corrige este problema.\\n2. Aplicar este parche: https://github.com/apache/brpc/pull/3354\\n\\nNota:\\nLa correcci\u00f3n rechaza los arreglos RESP vac\u00edos como comandos Redis no v\u00e1lidos y reemplaza el CHECK interno de \u00edndice por un error de an\u00e1lisis expl\u00edcito, de modo que los flujos de comandos malformados no puedan pasar a una escritura en un vector indexado."}], "lastModified": "2026-10-30T14:17:06.653", "sourceIdentifier": "security@apache.org"}