CVE-2026-82953

{"id": "CVE-2026-82953", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-82953", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-10-26T13:55:30.778417Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "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-21T13:20:03.560", "references": [{"url": "https://github.com/apache/brpc/pull/3508", "source": "security@apache.org"}, {"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-476"}]}], "descriptions": [{"lang": "en", "value": "NULL pointer dereference in the RTMP protocol implementation in Apache bRPC (version < 1.18.0) on all platforms allows remote attackers to crash the server (denial of service) via a crafted createStream command.\n\nRoot Cause:\nWhen an RTMP service rejects a createStream request by returning a null stream from RtmpService::NewStream(), the server sends an error response to the client. If writing this rejection response fails (for example, because the client closes the connection immediately after sending the createStream command), the error-handling path in RtmpChunkStream::OnCreateStream() dereferences the null stream pointer to access stream->_onfail_id, causing the process to crash.\n\nAffected Scenarios:\nRun an Apache bRPC RTMP server whose RtmpService::NewStream() may return null (i.e., the service rejects createStream requests). A remote client that sends a createStream command and then closes the connection before the rejection response is written can crash the server.\n\nHow to Fix:\n(Choose one of the following options)\n1. Upgrade bRPC to version 1.18.0, which fixes this issue.\n2. Apply this patch: https://github.com/apache/brpc/pull/3508"}, {"lang": "es", "value": "Desreferenciaci\u00f3n de puntero NULL en la implementaci\u00f3n del protocolo RTMP en Apache bRPC (versiones anteriores a la 1.18.0) en todas las plataformas permite a atacantes remotos bloquear el servidor (denegaci\u00f3n de servicio) mediante un comando createStream manipulado.\\n\\nCausa ra\u00edz:\\nCuando un servicio RTMP rechaza una solicitud createStream devolviendo un flujo nulo desde RtmpService::NewStream(), el servidor env\u00eda una respuesta de error al cliente. Si la escritura de esta respuesta de rechazo falla (por ejemplo, porque el cliente cierra la conexi\u00f3n inmediatamente despu\u00e9s de enviar el comando createStream), la ruta de manejo de errores en RtmpChunkStream::OnCreateStream() desreferencia el puntero de flujo nulo para acceder a stream -> _onfail_id, provocando el bloqueo del proceso.\\n\\nEscenarios afectados:\\nEjecutar un servidor RTMP de Apache bRPC cuyo RtmpService::NewStream() pueda devolver null (es decir, el servicio rechaza solicitudes createStream). Un cliente remoto que env\u00eda un comando createStream y luego cierra la conexi\u00f3n antes de que se escriba la respuesta de rechazo puede bloquear el servidor.\\n\\nC\u00f3mo corregir:\\n(Elija una de las siguientes opciones)\\n1. Actualizar bRPC a la versi\u00f3n 1.18.0, que corrige este problema.\\n2. Aplicar este parche: https://github.com/apache/brpc/pull/3508"}], "lastModified": "2026-10-26T21:10:00.170", "sourceIdentifier": "security@apache.org"}