Summary
LightLLM through version 1.2.0 contains an authentication bypass in the
/pd_register WebSocket endpoint. An unauthenticated attacker may register
unauthorized nodes, receive prompts routed to a malicious socket, disrupt
legitimate node registrations, or cause the PD Master to contact internal
network addresses when peer validation is absent.
Affected context
The vulnerability occurs in deployments that expose or otherwise make the
/pd_register WebSocket endpoint reachable without effective authentication.
Risk is increased when registration data is accepted without validating the
claimed peer address and when the PD Master trusts newly registered nodes for
routing or follow-up requests.
Exploit preconditions
- Attack surface: The
/pd_registerWebSocket endpoint - Required access: Network reachability to the endpoint; valid credentials
are not required when authentication is bypassed
- Trigger point: Processing of a node-registration message
- Why exploitation is possible: The endpoint accepts registration state
without reliably authenticating the caller or validating the associated peer
address
Why this happens
The underlying bug is an authentication enforcement failure mapped to
CWE-306: Missing Authentication for Critical Function. A node-registration
operation that changes trusted routing state is exposed without a mandatory,
server-side identity check. The absence of peer-address validation further
allows attacker-controlled registration metadata to influence where traffic
is routed or where subsequent internal requests are sent.
Potential impact
- Attackers may register arbitrary nodes with the PD Master
- User prompts may be disclosed to attacker-controlled sockets
- Legitimate nodes may be displaced, causing denial of service
- The PD Master may be induced to contact internal network addresses
- Distributed inference workloads may be disrupted or redirected
- Sensitive service metadata may be exposed through unauthorized routing
General mitigation guidance
Mitigation generally focuses on making node registration authenticated,
authorized, and strictly validated by default.
Common defensive patterns include:
- Require strong mutual authentication for registration connections
- Authorize registrations against an explicit node identity or allowlist
- Validate peer addresses server-side and reject inconsistent or
attacker-controlled routing metadata
- Treat registration messages as untrusted input and enforce a strict schema
- Limit which network destinations the PD Master can contact
- Apply least-privilege service accounts and network policies
- Avoid routing sensitive prompts to nodes that have not completed trust
verification
- Use secure connection defaults and prevent unauthenticated fallback paths
How teams detect issues like this
Organizations can look for this weakness through:
- Static analysis and code review checks for WebSocket handlers that mutate
cluster or routing state before authentication
- Tests that verify unauthenticated registration attempts are rejected
- Review of peer-address parsing, hostname resolution, and destination
validation logic
- Monitoring for unexpected node registrations, rapid replacement of known
nodes, or registrations from unauthorized network locations
- Network policy checks that restrict control-plane services from reaching
unnecessary internal destinations
- Automated security review tools that flag missing authentication and
server-side authorization at sensitive endpoints

