ioFog Controller WebSocket JWT Bypass Leading to Admin Access

Executive Summary

This vulnerability affects Eclipse ioFog Controller versions 3.8.0 through 3.9.1. It allows an attacker to bypass authentication by forging a JWT token with admin privileges. The WebSocket server does not verify the token's signature, issuer, audience, or expiration during upgrades on exec and log routes. This enables unauthorized access to execute commands or view logs on any microservice or fog node if the UUID is known.

Useful 0 Not Useful 0

Detection Guidance

Check if your Eclipse ioFog Controller version is between 3.8.0 and 3.9.1. Monitor WebSocket traffic on ports like 51121 for unauthorized exec or log sessions. Look for JWT tokens without proper signature verification in WebSocket upgrade requests.

Useful 0 Not Useful 0

Impact Analysis

An attacker can gain admin-level access without credentials, allowing remote command execution on managed workloads and unauthorized access to sensitive logs. This could lead to full control over microservices or fog nodes, data breaches, or service disruption. Exploitation requires only network access to the Controller API port.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection requirements and HIPAA's security rules for protected health information. The lack of proper authentication and authorization controls may result in non-compliance with these regulations, potentially leading to legal penalties and reputational damage.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade to Eclipse ioFog Controller version 3.9.2 or later once available. Block or restrict WebSocket access to the exec and log routes until patched. Implement network-level controls to limit access to the Controller API port.

Useful 0 Not Useful 0