9.8
Critique
CVE-2026-113620 In Eclipse ioFog Controller versions 3.8.0 through 3.9.1, operator WebSocket upgrades on the exec and log routes do…
Description
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| Eclipse ioFog 3.8 | 3.8.0 → 3.9.1 | Pas de correctif indiqué |
Références
- gitlab.eclipse.org gitlab.eclipse.org
- gitlab.eclipse.org gitlab.eclipse.org
- gitlab.eclipse.org gitlab.eclipse.org
- gitlab.eclipse.org gitlab.eclipse.org
Chronologie
- Publiée
- Dernière modification
Autres CVE de Eclipse ioFog
Les 4 CVE de Eclipse ioFog →
CVE-2026-113644
iofogctl command injection via Controller provisioning response
5.5
Moyenne
CVE-2026-115216
Eclipse ioFog Operator disables TLS certificate verification when sending Controller and OIDC credentials
9.1
Critique
CVE-2026-113619
In Eclipse ioFog Controller versions 3.8.0 through 3.9.1, POST, PUT, and PATCH bodies on routes that enable template…
7.5
Élevée