CVE-2026-84748

{
  "id": "CVE-2026-84748",
  "sourceIdentifier": "[email protected]",
  "published": "2026-10-21T13:20:03.997",
  "lastModified": "2026-10-30T15:16:56.313",
  "vulnStatus": "Deferred",
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Improper authorization in Apache bRPC (versions < 1.18.0) on all platforms allows remote attackers to access builtin services through the public port.\n\nRoot Cause:\nServerOptions.internal_port is documented to make builtin services (and Tabbed services) reachable only from the internal port, and the HTTP/h2 dispatch path enforced this. However, all protobuf-based protocol dispatch paths (baidu_std, hulu_pbrpc, sofa_pbrpc, and the nshead-based protocols public_pbrpc, nshead_mcpack, nova_pbrpc and ubrpc2pb) computed the security_mode flag but never enforced it between method resolution and method invocation. Since builtin services share the method map with user services, a client able to reach the public port could invoke builtin services such as brpc.vars or hotspots by name over these pb protocols and disclose sensitive runtime information (metrics, flags, profiler data) that the operator intended to expose only via the internal port.\n\nAffected Scenarios:\nUse a bRPC server with ServerOptions.internal_port configured (or with builtin/Tabbed services otherwise expected to be gated by it) while the public port is reachable from an untrusted network and any pb-based protocol is enabled.\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/3511"
    },
    {
      "lang": "es",
      "value": "Autorización incorrecta en Apache bRPC (versiones anteriores a la 1.18.0) en todas las plataformas permite a atacantes remotos acceder a los servicios incorporados a través del puerto público.\\n\\nRoot Cause:\\nServerOptions.internal_port está documentado para que los servicios incorporados (y los servicios Tabbed) sean accesibles solo desde el puerto interno, y la ruta de despacho HTTP/h2 lo aplicaba. Sin embargo, todas las rutas de despacho de protocolos basados en protobuf (baidu_std, hulu_pbrpc, sofa_pbrpc y los protocolos basados en nshead public_pbrpc, nshead_mcpack, nova_pbrpc y ubrpc2pb) calculaban la bandera security_mode pero nunca la aplicaban entre la resolución del método y la invocación del método. Dado que los servicios incorporados comparten el mapa de métodos con los servicios de usuario, un cliente que pueda alcanzar el puerto público podría invocar servicios incorporados como brpc.vars o hotspots por nombre mediante estos protocolos pb y revelar información sensible en tiempo de ejecución (métricas, banderas, datos del profiler) que el operador pretendía exponer solo a través del puerto interno.\\n\\nAffected Scenarios:\\nUtilizar un servidor bRPC con ServerOptions.internal_port configurado (o con servicios incorporados/Tabbed que de otro modo se esperaría que estuvieran restringidos por él) mientras el puerto público es accesible desde una red no confiable y cualquier protocolo basado en pb está habilitado.\\n\\nHow to Fix:\\n1. Actualizar bRPC a la versión 1.18.0, que corrige este problema.\\n2. Aplicar este parche: https://github.com/apache/brpc/pull/3511"
    }
  ],
  "affected": [
    {
      "source": "[email protected]",
      "affectedData": [
        {
          "vendor": "Apache Software Foundation",
          "product": "Apache bRPC",
          "defaultStatus": "unaffected",
          "collectionURL": "https://github.com",
          "packageName": "apache/brpc",
          "packageURL": "pkg:github/apache/brpc",
          "versions": [
            {
              "version": "0",
              "lessThan": "1.18.0",
              "versionType": "semver",
              "status": "affected"
            }
          ]
        }
      ]
    }
  ],
  "metrics": {
    "cvssMetricV31": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary",
        "cvssData": {
          "version": "3.1",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "attackVector": "NETWORK",
          "attackComplexity": "LOW",
          "privilegesRequired": "NONE",
          "userInteraction": "NONE",
          "scope": "UNCHANGED",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "availabilityImpact": "NONE"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "timestamp": "2026-10-30T14:39:52.195784Z",
          "id": "CVE-2026-84748",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "version": "2.0.3"
        }
      }
    ]
  },
  "weaknesses": [
    {
      "source": "[email protected]",
      "type": "Secondary",
      "description": [
        {
          "lang": "en",
          "value": "CWE-285"
        }
      ]
    }
  ],
  "references": [
    {
      "url": "https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb",
      "source": "[email protected]"
    }
  ]
}