In Eclipse ioFog Controller versions 3.8.0 through 3.9.1, operator WebSocket upgrades on the exec and log routes do not verify the bearer JWT. The payload is decoded and its groups or roles are used as RBAC subjects. A self-minted token whose groups contain admin matches the built-in admin role, with no account and no RoleBinding.
The attacker can open an exec or log session for a microservice or fog whose UUID they already know. HTTP routes are not affected: they verify the token before RBAC. Agent WebSockets verify the fog token and are not affected.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
eclipse foundation:eclipse iofog
References 4
https://gitlab.eclipse.org/security/cve-assignment/-/work_items/468
emo@eclipse.org
https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1267
emo@eclipse.org
https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1269
emo@eclipse.org
https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1270
emo@eclipse.org