Routinator terminates when RTR connection is reset too quickly after opening

Vulnerability

Due to a mistake in error checking, Routinator terminates when an incoming RTR connection is reset by the peer too quickly after opening. This affects Routinator versions up to and including 0.13.1 [4].

Exploitation

An attacker can cause Routinator to terminate by simply opening an RTR connection and resetting it quickly. No authentication or high privileges are required; the attacker only needs network access to send a reset [4].

Impact

Successful exploitation leads to a denial of service (DoS) as Routinator exits, disrupting RPKI validation services [4].

Mitigation

Upgrade to Routinator version 0.13.2 or later, which correctly handles such connections. No workarounds are available [4].