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.
The certificate chain must end at a root in the device endpoint's trust store. With DEVICE_SSL_CACERTFILE unset, which is the default from 2.0.0, the trust store holds the public roots from CAStore. With DEVICE_SSL_CACERTFILE set to a bundle that holds a root which signs device certificates, any certificate from that root whose CA is not registered is sufficient, including the certificate of a deleted device.
The retry in Erlang/OTP ssl was confirmed on Erlang/OTP 28.3, 29.0 and 29.1. Earlier releases were not checked.
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.