Covenant C2 SignalR Hub Unauthenticated Access Vulnerability

Technical Analysis

The vulnerability stems from CovenantHub, a SignalR hub within the Covenant C2 framework, being registered without an [Authorize] attribute, permitting unauthenticated remote invocation of the CreateHttpListener method. This call returns a legitimately signed JWT token, which attackers can then use to authenticate against the full operator REST API—effectively achieving complete administrative takeover of the C2 server with no prior credentials. Given a CVSS score of 9.1, exploitation requires only network access to the exposed SignalR endpoint and results in disclosure of active agent ('grunt') sessions, stored operator credentials, compiled payload binaries, and full operational event history. This is particularly dangerous in red team or adversary emulation environments, as compromise of the C2 infrastructure itself can expose ongoing engagements, client environments, and stolen credentials from multiple targets. If Covenant or similar C2 frameworks are used to manage AI agent-based automation tasks (e.g., orchestrating agentic red-team tooling, automated payload generation, or LLM-driven decision loops for post-exploitation), a compromised C2 backend could allow attackers to hijack agent task queues, exfiltrate API keys embedded in grunt configurations, or inject malicious commands into agent-driven workflows, making this agent-relevant for any AI-augmented offensive security tooling built atop Covenant.

Affected Systems

Covenant C2 framework, all versions through 0.6, specifically deployments exposing the CovenantHub SignalR endpoint over network-accessible interfaces without additional network-layer access controls.

Indicators of Compromise

• No specific file hashes, IPs, or domains published; indicators are environment-specific (exposed Covenant SignalR hub endpoint, typically /covenanthub or similar path, and anomalous CreateHttpListener invocations in Covenant server logs)

Remediation Steps

1. 1

   Upgrade Covenant

   Update to a patched version of Covenant beyond 0.6 once available, or apply vendor/community patches enforcing [Authorize] on CovenantHub.

2. 2

   Restrict network access

   Limit access to the Covenant server's SignalR hub and operator API to trusted internal networks or VPN-only access; do not expose to the public internet.

3. 3

   Rotate credentials and tokens

   Immediately rotate JWT signing secrets, operator credentials, and any credentials stored within Covenant grunts if exposure is suspected.

4. 4

   Monitor for unauthorized access

   Review Covenant server logs for unauthenticated CreateHttpListener calls or unexpected operator API access patterns.

5. 5

   Implement network segmentation

   Place C2 infrastructure behind firewalls, mutual TLS, or IP allowlisting to prevent unauthenticated external connections to management interfaces.