{
  "affected": [
    {
      "affectedData": [
        {
          "product": "TrustTunnel",
          "vendor": "TrustTunnel",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.9.115"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:adguard:trusttunnel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "08F7E28C-244F-4FAE-9EDF-127191A1FED8",
              "versionEndExcluding": "0.9.115",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "TrustTunnel is an open-source VPN protocol with a rule bypass issue in versions prior to 0.9.115. In `tls_listener.rs`, `TlsListener::listen()` peeks 1024 bytes and calls `extract_client_random(...)`. If `parse_tls_plaintext` fails (for example, a fragmented/partial ClientHello split across TCP writes), `extract_client_random` returns `None`. In `rules.rs`, `RulesEngine::evaluate` only evaluates `client_random_prefix` when `client_random` is `Some(...)`. As a result, when extraction fails (`client_random == None`), any rule that relies on `client_random_prefix` matching is skipped and evaluation falls through to later rules. As an important semantics note: `client_random_prefix` is a match condition only. It does not mean \"block non-matching prefixes\" by itself. A rule with `client_random_prefix = ...` triggers its `action` only when the prefix matches (and the field is available to evaluate). Non-matches (or `None`) simply do not match that rule and continue to fall through. The vulnerability is fixed in version 0.9.115."
    },
    {
      "lang": "es",
      "value": "TrustTunnel es un protocolo VPN de c\u00f3digo abierto con un problema de omisi\u00f3n de reglas en versiones anteriores a la 0.9.115. En `tls_listener.rs`, `TlsListener::listen()` examina 1024 bytes y llama a `extract_client_random(...)`. Si `parse_tls_plaintext` falla (por ejemplo, un ClientHello fragmentado/parcial dividido en varias escrituras TCP), `extract_client_random` devuelve `None`. En `rules.rs`, `RulesEngine::evaluate` solo eval\u00faa `client_random_prefix` cuando `client_random` es `Some(...)`. Como resultado, cuando la extracci\u00f3n falla (`client_random == None`), cualquier regla que dependa de la coincidencia de `client_random_prefix` se omite y la evaluaci\u00f3n pasa a reglas posteriores. Como una nota sem\u00e1ntica importante: `client_random_prefix` es solo una condici\u00f3n de coincidencia. No significa \u0027bloquear prefijos no coincidentes\u0027 por s\u00ed mismo. Una regla con `client_random_prefix = ...` activa su `acci\u00f3n` solo cuando el prefijo coincide (y el campo est\u00e1 disponible para evaluar). Las no-coincidencias (o `None`) simplemente no coinciden con esa regla y contin\u00faan pasando. La vulnerabilidad est\u00e1 corregida en la versi\u00f3n 0.9.115."
    }
  ],
  "id": "CVE-2026-24904",
  "lastModified": "2026-06-17T10:23:47.003",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-24904",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-01-29T21:34:05.106512Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-01-29T22:15:55.047",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/TrustTunnel/TrustTunnel/commit/aa5060145506952b9431b0ed3edb52bb6c08d9a6"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Exploit",
        "Patch",
        "Vendor Advisory"
      ],
      "url": "https://github.com/TrustTunnel/TrustTunnel/security/advisories/GHSA-fqh7-r5gf-3r87"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-284"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}