Summary
ArcadeDB's Redis wire-protocol plugin does not require authentication before processing client commands, allowing unauthenticated network attackers to access server databases. An attacker who can reach the Redis port may read, create, modify, or delete data across databases without passing the platform's intended security controls.
Affected context
The vulnerability occurs in ArcadeDB deployments that expose or otherwise permit access to the Redis wire-protocol plugin without an effective authentication boundary. It becomes risky when the Redis port is reachable by untrusted clients and the plugin accepts database commands before verifying credentials or authorizing the requested operation.
Exploit preconditions
- Attack surface: The ArcadeDB Redis wire-protocol listener
- Required access: Network connectivity to the Redis port; valid credentials are not required
- Trigger point: Submission of Redis protocol commands to the listener
- Why exploitation is possible: The plugin processes requests without first enforcing authentication or an equivalent access-control check
Why this happens
The underlying defect is an authentication enforcement failure. A network-facing protocol handler permits sensitive operations to proceed without establishing the caller's identity, mapping to CWE-306: Missing Authentication for Critical Function. The insecure pattern is placing command processing ahead of mandatory authentication and authorization checks, allowing anonymous clients to invoke operations intended only for trusted users.
Potential impact
- Unauthenticated attackers may read data from any accessible database
- Attackers could insert or alter records and database contents
- Attackers may delete data, causing loss of availability or integrity
- Sensitive information could be disclosed
- Compromised data could affect applications and downstream services
- The exposed service could become an entry point for broader environment compromise
General mitigation guidance
Mitigation generally focuses on enforcing authentication and authorization before any protocol command is processed.
Common defensive patterns include:
- Require strong authentication for every Redis protocol connection
- Apply per-database and per-operation authorization rather than relying only on network location
- Bind administrative protocol listeners to trusted interfaces or isolated networks
- Restrict access with firewalls, security groups, and private service exposure
- Disable unused wire-protocol plugins and listeners
- Run the database service with least-privilege operating-system and platform permissions
- Monitor and rate-limit access to administrative protocol endpoints
How teams detect issues like this
Organizations can identify this class of issue through:
- Configuration reviews that verify authentication is mandatory for every network-facing protocol
- Static and architectural analysis checking that authentication middleware precedes command dispatch
- Code review signals such as public listeners with direct access to data-management handlers
- Integration tests that attempt unauthenticated read, write, and delete operations and expect rejection
- Network scans and policy checks for exposed Redis-compatible ports
- Runtime monitoring for anonymous connections and destructive commands
- Automated security review tools that flag missing authentication on sensitive endpoints

