Summary
Redpanda deployments may expose the Admin API on all network interfaces while authentication is disabled by default. An attacker who can reach port 9644 without credentials may gain administrative control over broker accounts and cluster settings, potentially disrupting partition replication.
Affected context
The vulnerability occurs in Redpanda deployments where the Admin API listens on
0.0.0.0:9644 and admin_api_require_auth remains disabled. In this configuration,
network-reachable clients may submit administrative requests without authentication,
allowing access to sensitive broker and cluster-management operations.
Exploit preconditions
- Attack surface: Redpanda Admin API exposed on TCP port 9644
- Required access: Network connectivity to the Admin API; valid credentials may not be required when authentication is disabled
- Trigger point: An administrative API request is processed without an authentication check
- Why exploitation is possible: The service treats unauthenticated callers as administrative users when the authentication requirement is not enabled
Why this happens
The underlying issue is missing authentication enforcement on a privileged management
interface. Binding the Admin API to all interfaces increases its network exposure, while
a permissive default allows requests to proceed without verifying the caller's identity.
This behavior maps to CWE-306: Missing Authentication for Critical Function, because
sensitive administrative operations can be invoked without an authentication mechanism.
Potential impact
- Attackers may create or delete broker accounts
- Cluster configuration may be changed without authorization
- Partition replication may be disrupted
- Cluster availability and data-management operations could be affected
- Unauthorized administrative control may enable further compromise
General mitigation guidance
Mitigation generally focuses on enforcing authentication for every privileged Admin API
operation and reducing the interface's network exposure.
Common defensive patterns include:
- Require strong authentication by default for administrative APIs
- Bind management interfaces only to trusted management networks or loopback addresses where practical
- Place the Admin API behind network access controls and authenticated gateways
- Apply least-privilege administrative roles and separate broker-management permissions
- Disable or restrict administrative endpoints that are not required
- Use encrypted transport and centralized authorization policies for management traffic
- Treat unauthenticated administrative access as a deployment-policy violation
How teams detect issues like this
Organizations can detect this class of issue through:
- Configuration analysis for disabled Admin API authentication requirements
- Network scans identifying Redpanda management services exposed beyond trusted networks
- Static and infrastructure-as-code checks for management listeners bound to all interfaces
- Code and configuration review signals showing privileged endpoints without authentication middleware
- Policy enforcement preventing unauthenticated access to administrative ports
- Monitoring for unexpected broker-account changes, cluster configuration updates, or replication-setting changes
Automated security review tools may help identify exposed management interfaces and insecure authentication defaults.

