The vulnerability arises because the Remote Collector's configuration generated through n2os-tui disables TLS certificate verification when connecting to the upstream Guardian or CMC. Since there is no option to enable TLS verification, an attacker positioned between the Remote Collector and the Guardian or CMC can perform man-in-the-middle attacks. This can lead to theft of synchronization tokens, server impersonation, injection of spoofed data such as false asset or vulnerability information, and disruption of data synchronization between components.

An attacker exploiting this vulnerability can intercept and manipulate communications between the Remote Collector and the Guardian or CMC. This can result in theft of sensitive sync tokens, unauthorized impersonation of servers, injection of false data into the system, and disruption of data flow, potentially undermining the integrity and reliability of the monitoring infrastructure.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or configuration option is provided, users should be aware that TLS certificate verification is disabled by design in this scenario. No vendor advisory or patch information is currently available to address this issue.