Cpe:2.3:a:pikiwidb:pika:3.5.7:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3apikiwidbpika3.5.7/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 02 Sep 2026 05:11:29 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAuthentication Bypass in PikiwiDB Pika Replication Serverhttps://feed.craftedsignal.io/briefs/2026-09-pikiwidb-auth-bypass/Wed, 02 Sep 2026 05:11:29 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-pikiwidb-auth-bypass/PikiwiDB Pika 3.5.7 suffers from an authentication bypass in its protobuf replication server, allowing unauthenticated remote attackers to synchronize data and manipulate replica nodes.PikiwiDB (Pika) version 3.5.7 contains a critical authentication bypass vulnerability (CVE-2026-84700) within its internal protobuf replication server. The service exposes a secondary port, calculated as the default client port plus 2000 (e.g., 11221 for a default port of 9221), which fails to properly enforce authentication. While the Pika 'requirepass' configuration is intended to protect the replication interface, only the MetaSync handler specifically validates credentials. The frame dispatcher (DealMessage) fails to verify authentication or session state before routing incoming messages, such as TrySync, DBSync, BinlogSync, and RemoveSlaveNode, to their respective handlers. Consequently, an unauthenticated remote attacker can connect directly to the exposed replication port to exfiltrate full-sync snapshots, monitor live write streams, or disrupt database replication by removing slave nodes, regardless of the security settings configured on the primary client interface.

Impact

Successful exploitation allows for the unauthorized exfiltration of sensitive database content and full-sync snapshots, potentially leading to complete data exposure. Attackers can also disrupt database availability and integrity by force-removing legitimate replica nodes. This vulnerability affects Pika 3.5.7, which is often deployed in high-performance storage environments where data replication is critical.

Recommendation

  1. Restrict network access to the PikiwiDB replication port to authorized internal nodes only via firewall rules, as the service does not enforce authentication.
  2. Audit environment configurations for Pika 3.5.7 deployments and restrict management/replication port exposure from public or untrusted network segments.
  3. Monitor internal network traffic for unexpected connections originating from non-replica nodes to the calculated Pika replication port (default client port + 2000).
]]>highadvisory