A critical authentication bypass in PikiwiDB allows unauthenticated remote attackers to access sensitive database replication streams and perform unauthorized administrative actions.

The application exposes an internal protobuf replication port that fails to enforce authentication for non-MetaSync requests. Because the frame dispatcher does not validate the authentication state before routing commands such as TrySync or DBSync, an unauthenticated remote attacker can interface directly with the replication server.

The ability to access replication streams grants an attacker full visibility into the database contents, leading to a complete compromise of data confidentiality. Furthermore, the capacity to issue commands like RemoveSlaveNode can cause significant service disruption and data loss, impacting business continuity. Given the CVSS score of 8.6, this vulnerability represents a high-risk entry point that could be leveraged for large-scale data exfiltration.

Immediate Action: Update PikiwiDB to a version beyond 4.0.4-alpha where authentication is strictly enforced across all replication handlers.

Proactive Monitoring: Monitor network traffic for unauthorized connections to ports derived from the client port plus 2000, and audit logs for unexpected MetaSync or replication command activity.

Compensating Controls: Implement strict network access control lists (ACLs) to ensure the replication port is only accessible to trusted internal replica nodes, effectively isolating the management interface from external networks.

Public Exploit Available: Unknown.

This vulnerability poses a severe threat to database integrity and confidentiality. Administrators must prioritize updating the affected software immediately. If an update cannot be applied instantly, network-level segmentation is required to prevent unauthorized access to the replication port, as the application's internal authentication mechanism is fundamentally broken in the affected versions.