Description
PikiwiDB (Pika) v3.5.7 exposes an internal protobuf replication server on a port derived from the client port plus 2000 (e.g. 11221 when the default client port 9221 is used) that does not authenticate incoming requests. Although requirepass is intended to gate replication — a slave presents it as masterauth inside its MetaSync request — only the MetaSync handler (HandleMetaSyncRequest) validates it; the frame dispatcher (DealMessage) does not require a completed or attempted MetaSync before routing other message types to their handlers. As a result, an unauthenticated remote attacker can connect directly to the replication port and issue TrySync, DBSync, BinlogSync, and RemoveSlaveNode requests, obtaining the full-sync snapshot and live write stream and removing replica nodes, even when requirepass is configured.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
OpenAtomFoundation pikiwidb
Default version status: unaffected
0 to ≤ 4.0.4-alphaaffected
pkg:github/OpenAtomFoundation/pikiwidbReferences
- https://github.com/OpenAtomFoundation/pikiwidb ↗
- https://github.com/OpenAtomFoundation/pikiwidb/issues/3270 ↗
- https://github.com/OpenAtomFoundation/pikiwidb/blob/v3.5.7/src/pika_repl_server_conn.cc ↗
- https://www.vulncheck.com/advisories/pika-unauthenticated-replication-access-via-internal-protobuf-port ↗