Summary
An improper authorization flaw in the /tequilapi/config/user endpoint of Mysterium Node allows unauthenticated users to overwrite node configuration via crafted POST requests.
If exposed, this can enable a full node takeover by letting an attacker change critical operational settings without prior authentication.
Affected context
This vulnerability affects Mysterium Node deployments that expose the /tequilapi/config/user HTTP endpoint without an effective authentication or authorization layer.
It is most relevant when the API is reachable over a network interface (e.g., LAN, VPN, or internet) and the node relies on configuration values for access control, routing, or operational behavior.
Misconfigured firewalls, reverse proxies, or default installations that publish the TequilAPI externally may increase the risk.
Exploit preconditions
- Attack surface: Network-accessible TequilAPI endpoint
/tequilapi/config/user - Required access: Ability to reach the node over HTTP(S); no valid credentials required
- Trigger point: Sending a crafted POST request that supplies attacker-controlled configuration values
- Why exploitation is possible: The endpoint updates user configuration without enforcing proper authorization checks, allowing unauthenticated callers to modify sensitive settings that control node behavior
Why this happens
The issue stems from missing or incomplete authorization logic on a configuration management endpoint.
The /tequilapi/config/user handler accepts state-changing POST requests but does not verify that the caller is an authenticated and authorized node owner or administrator.
This maps to CWE-862: Missing Authorization, where the application exposes a privileged operation without confirming that the user has permission to perform it.
At a design level, configuration write operations were not consistently treated as security-sensitive, resulting in a trust-by-default pattern for any reachable client.
Potential impact
- Attackers may overwrite node configuration to redirect traffic or alter service behavior.
- Attackers may disable security-related options, increasing exposure to other attacks.
- Attackers could configure the node to participate in abusive or malicious activity.
- Attackers can potentially lock out the legitimate operator by changing access or control settings.
- Attackers may use the compromised node as a foothold for broader network reconnaissance.
General mitigation guidance
Mitigation generally focuses on enforcing robust access control around all configuration-changing endpoints and reducing unnecessary exposure of management APIs.
Helpful patterns include:
- Requiring strong authentication and explicit authorization for any state-changing API, especially configuration writes.
- Implementing a central authorization layer rather than per-endpoint ad hoc checks, ensuring all handlers inherit consistent policy.
- Treating node configuration as a sensitive resource and enforcing least-privilege principles for any process or user that can modify it.
- Restricting management API exposure using network-layer controls (firewalls, bind-to-localhost, VPN-only access) so only trusted administrators can connect.
- Adding secure defaults that deny unauthenticated configuration changes and require explicit opt-in for remote management.
How teams detect issues like this
Detection efforts can focus on both code-level analysis and runtime monitoring:
- Static analysis and code review to identify HTTP handlers that perform configuration writes or other privileged actions without invoking a standard authentication/authorization middleware.
- Review of routing and handler registration to ensure all TequilAPI endpoints are covered by consistent access control policies.
- Log analysis for unusual or unauthenticated POST requests to
/tequilapi/config/user, including spikes in configuration changes or access from unexpected IP ranges. - Security testing and API fuzzing to verify that configuration endpoints reject requests without valid credentials.
- Integration of automated security scanners into CI/CD to flag missing authorization checks on sensitive operations.

