Descrizione

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in device certificate verification in nerves-hub nerves_hub_web allows an unauthenticated remote attacker to cause a denial of service via a TLS client certificate whose CA is not registered. When a client certificate chains to a root in the device endpoint's trust store but no CA in the chain is registered in NervesHub, NervesHub.SSL.decide/2 refuses it with the reason :unknown_ca. Erlang/OTP ssl reads that reason as a missing trust anchor, looks for an alternative root, finds the same root and validates again without end. The handshake process queries the database on each pass and keeps running after the client disconnects, until the node restarts. The device endpoint trusts the public roots from CAStore unless DEVICE_SSL_CACERTFILE is set, so a client certificate from a public CA whose chain allows client authentication is sufficient. A chain that ends at a root outside the trust store is refused once. This issue affects nerves_hub: from 1.0.0 before 2.5.4.

Testo originale del record CVE (in inglese).

Come correggere

Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 8.2, EPSS 0.4% (percentile 34).

Versioni da aggiornare

  • nerves-hub nerves_hub_web: vulnerabili le versioni dalla 1.0.0 precedenti alla 2.5.4 → aggiornare alla 2.5.4 o successiva.

Indicazioni del vendor

Workaround (testo originale del vendor):

Set DEVICE_SSL_CACERTFILE to a bundle that holds no public root and no root that signs device certificates, for example a file with one self-signed certificate made for this purpose. A certificate from an unregistered CA is then refused once and the handshake ends. Devices whose certificate or CA is registered in NervesHub continue to connect. Restarting a node ends the handshakes that are already stuck on it.

Mitigazioni temporanee

Da applicare solo se non è possibile aggiornare subito:

  • Applicare rate limiting e limiti sulle risorse a monte del servizio e monitorarne la disponibilità.

Verifica

  1. Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
  2. Confrontare la versione installata con quelle indicate sopra.
  3. Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
  4. Ripetere la scansione per confermare la correzione.

Configurazioni interessate

VendorProdottoVersioni vulnerabiliCorretta in
nerves-hub nerves_hub_web ≥ 1.0.0 < 2.5.4 2.5.4

Riferimenti