Summary
Knowns versions before 0.30.0 expose the management API without authentication on all network interfaces, and fresh installations require no password. An unauthenticated attacker may provision a public tunnel through /api/tunnel/start and republish the API at an internet-accessible address.
Affected context
The vulnerability occurs in Knowns deployments using versions before 0.30.0 when the management API is bound to all network interfaces by default. Fresh installations may lack password protection, allowing network-reachable users to access management endpoints without proving their identity.
Exploit preconditions
- Attack surface: Network-accessible Knowns management API
- Required access: Ability to send HTTP requests to the exposed API; no credentials may be required on fresh installations
- Trigger point: Unauthenticated access to
/api/tunnel/start - Why exploitation is possible: The management API does not enforce authentication before allowing tunnel provisioning and API republishing
Why this happens
The underlying issue is an authentication enforcement failure mapped to CWE-306: Missing Authentication for Critical Function. A management interface exposes security-sensitive functionality without requiring a valid identity, while its default network binding broadens reachability. As a result, an unauthenticated request can invoke administrative behavior intended only for trusted operators.
Potential impact
- An attacker may provision a public tunnel to the management service
- The management API could become reachable from the public internet
- Unauthorized users may access or modify exposed administrative functionality
- Sensitive configuration or operational data could be disclosed
- The service may be abused as an entry point for further compromise
General mitigation guidance
Mitigation generally focuses on enforcing authentication and reducing the management API's network exposure.
Common defensive patterns include:
- Require authentication and authorization for every management and tunnel-provisioning operation
- Use secure-by-default configuration that binds management interfaces to a restricted address
- Disable public tunnel creation unless explicitly required and authorized
- Place administrative endpoints behind an allowlisted network boundary or private access path
- Apply least-privilege permissions to management accounts and service identities
- Treat fresh-installation defaults as security-sensitive and require explicit credential setup
How teams detect issues like this
Organizations can look for:
- Static analysis and configuration checks that identify management routes lacking authentication middleware
- Code review signals involving administrative endpoints, tunnel creation, or public rebinding
- Tests verifying that unauthenticated requests receive denial responses for every privileged operation
- Network policy checks for management services listening on all interfaces
- Web and audit logs showing requests to
/api/tunnel/startwithout an authenticated principal - Policy enforcement preventing administrative APIs from being publicly reachable
Automated security review tools may help identify missing authorization checks and unsafe default bindings.

