Threats affecting pkg:github/AiSOC

AiSOC versions 12.1.0 up to but not including 23.3.0 have a missing authentication vulnerability that allows unauthenticated attackers to query the enrichment service via specific API routes. This flaw enables attackers to retrieve threat intelligence data and potentially consume commercial API quota by setting a force parameter.

AiSOC versions 5.1.0 before 12.0.0 contain an authentication bypass vulnerability in the realtime service internal endpoints POST /internal/agent-event and POST /internal/push. Attackers can post arbitrary events with spoofed tenant identifiers to broadcast malicious content over WebSocket and Redis SSE channels or send unauthorized notifications to registered devices.

AiSOC versions 7.2.0 up to but not including 12.0.0 have a critical OS command injection vulnerability in the actions service. This flaw allows authenticated users to inject special characters into command parameters, enabling execution of arbitrary commands on managed endpoints with SYSTEM or root privileges.

AiSOC versions 7.5.0 up to but not including 12.0.0 contain a vulnerability where a hard-coded cryptographic key is used for JWT verification in the realtime WebSocket and SSE service if the AISOC_REALTIME_JWT_SECRET environment variable is not set. This allows unauthenticated attackers to forge subscription tickets with arbitrary tenant identifiers, enabling unauthorized access to cross-tenant live alerts, cases, agent events, and graph updates via realtime endpoints.

AiSOC versions before 12.0.0 contain an authorization bypass vulnerability in the MSSP module that allows authenticated users to add arbitrary tenants to portfolios they own. Attackers can submit tenant UUIDs via the add_tenants_to_portfolio endpoint to claim unclaimed tenants and read their security alerts, incidents, and posture metrics without consent.

AiSOC versions 9.0.0 before 12.0.0 fail to enforce authentication on the response-action API endpoints when AISOC_DEV_MODE is enabled and AISOC_ACTIONS_SERVICE_TOKEN is empty in the default Docker Compose deployment. Unauthenticated attackers can list response-action integrations, submit and approve actions on behalf of arbitrary principals, and dispatch containment actions using vendor credentials.