AiSOC versions 7.5.0 before 12.0.0 use a hard-coded constant for JWT verification in the realtime WebSocket and SSE service when the AISOC_REALTIME_JWT_SECRET environment variable is not set. Unauthenticated attackers can forge subscription tickets with arbitrary tenant identifiers to access cross-tenant live alerts, cases, agent events and graph updates through the realtime endpoints.
Weakness
The product uses a hard-coded, unchangeable cryptographic key.
Potential Mitigations
References
- https://github.com/beenuar/AiSOC/blob/v11.2.0/services/realtime/src/auth.ts#L51-L59
- https://github.com/beenuar/AiSOC/commit/2f0e954f2febecb3720e6eadb017546c5d121c43
- https://github.com/beenuar/AiSOC/releases/tag/v12.0.0
- https://github.com/beenuar/AiSOC/security/advisories/GHSA-4m55-xhcm-wjcr
- https://www.vulncheck.com/advisories/aisoc-7.5.0-before-12.0.0-authentication-bypass-via-hard-coded-jwt-secret
- https://github.com/beenuar/AiSOC/security/advisories/GHSA-4m55-xhcm-wjcr