Skip to content

[security] - Autoheal incident API unauthenticated #97

Open

Description

@shieldx-bot
  • Description: services/shieldx-sandbox/autoheal/main.go exposes /autoheal/incident without any authentication or rate limiting. An external actor can fabricate incidents that trigger MeshController to launch replacement VMs via triggerRecovery, leading to resource exhaustion or unauthorized infrastructure changes.
  • Location: services/shieldx-sandbox/autoheal/main.go (handler registration) and shared/shieldx-common/core/autoheal/mesh_controller.go (HandleIncident/triggerRecovery).
  • Recommendation: Require strong auth (JWT/mTLS + RBAC) for incident submission, validate node identifiers, enforce quotas, and ensure recovery workflows verify origin before provisioning resources.
  • Done when: Unauthorized requests get 401/403, abuse tests cannot spawn incidents, and audit logs capture authenticated operators only.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededsecuritysystem security vulnerabilities

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions