Cpe:2.3:a:cc_connect:cc_connect:*:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3acc_connectcc_connect/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSat, 10 Oct 2026 15:55:34 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAuthentication Bypass in cc-connect MAX Platform Adapterhttps://feed.craftedsignal.io/briefs/2026-10-max-adapter-auth-bypass/Sat, 10 Oct 2026 15:55:34 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-max-adapter-auth-bypass/The MAX platform adapter in cc-connect version 1.5.0 and earlier allows unauthenticated attackers to forge webhook updates and execute arbitrary shell commands on the host system.The cc-connect application, specifically within the MAX platform adapter (platform/max/max.go), contains a critical missing authentication vulnerability (CVE-2026-108549). This vulnerability affects webhook mode when a webhook_secret is not configured. An attacker with network access to the webhook listener (default port 8080) can submit malicious, unauthenticated update payloads. By crafting these payloads to include administrative user_id values, an attacker can bypass authorization controls and invoke privileged functions, such as the /shell command, resulting in arbitrary command execution on the host operating system. This issue is particularly severe in environments where the service is exposed to the internet or untrusted internal networks without secondary authentication or restrictive network access control lists.

Attack Chain

  1. Attacker performs network reconnaissance to identify active listeners on TCP port 8080.
  2. Attacker interacts with the webhook listener to confirm the presence of the MAX platform adapter.
  3. Attacker identifies that the target environment lacks a configured webhook_secret in the platform/max/max.go implementation.
  4. Attacker constructs a malicious JSON payload mimicking a legitimate platform update.
  5. Attacker includes a high-privilege or administrator user_id within the forged payload.
  6. Attacker sends the payload to the /webhook endpoint (or equivalent listener path) via an HTTP POST request.
  7. The application fails to validate the request origin or authenticity, processing the forged payload as authorized.
  8. The adapter executes the requested privileged command, such as /shell, leading to full system compromise.

Impact

Successful exploitation allows remote, unauthenticated attackers to gain arbitrary code execution on the underlying host. This could lead to full system takeover, sensitive data exfiltration, or persistence within the environment. All versions of cc-connect up to and including 1.5.0 are affected.

Recommendation

  1. Upgrade cc-connect to a version beyond 1.5.0 that addresses the missing authentication in the MAX platform adapter immediately.
  2. If an immediate upgrade is not possible, ensure a robust webhook_secret is configured to enforce authentication on all webhook requests.
  3. Restrict network access to the webhook listener (default port 8080) to trusted IP addresses only using host-based firewalls or network security groups.
  4. Enable and monitor webserver logs (HTTP access logs) for POST requests to the /webhook endpoint occurring from unknown or external IP addresses.
]]>highadvisoryauthentication-bypasscveremote-code-execution