2026-09-06 · view entry permalink →
Dell Secure Connect Gateway DSA-2026-382: an unauthenticated request replayed indefinitely mints ADMIN tokens, and Dell ships no workaround for any of the 105 flaws
Dell's DSA-2026-382, released 2026-08-31 in its only revision to date, fixes 105 proprietary-code CVEs in Secure Connect Gateway 5.0, plus one third-party flaw in the BSAFE Crypto-J component (Dell PSIRT, 2026-08-31). Secure Connect Gateway is the on-premises component that collects telemetry and diagnostics from a customer's Dell server, storage and networking estate and carries remote-support sessions back to Dell, so it sits inside the estate with broad reach into it and an outbound path to the vendor. Three of the 105 score 9.0 or above; the remainder run from 2.4 to 8.2 and include further hard-coded credentials, certificate-validation bypasses, path traversal and command injection, most of them also reachable without authentication.
The one that changes the exposure calculation is CVE-2026-80172 (CVSS 9.8), an insufficient-verification-of-data-authenticity flaw. Dell's own description states that an unauthenticated attacker "can repeatedly reuse a captured request to generate ADMIN access and refresh tokens" and that "there is no nonce validation or time limit on requests, the attack can be performed indefinitely" (Dell PSIRT, 2026-08-31). A single request observed once, at any point in the gateway's history, remains a working administrative credential for as long as the gateway stays unpatched: there is no expiry to wait out and no session to terminate. CVE-2026-61410 (9.4) is a missing-authorization flaw that Dell describes as letting an attacker "execute commands remotely on a target system by sending a specially crafted request to the application, bypassing intended restrictions on code execution", reported alongside sibling flaws CVE-2026-61409 and CVE-2026-61408 by the researcher credited as Saltedfish. CVE-2026-61409 (7.3) is an OS command injection Dell also records as reachable by an unauthenticated attacker with remote access, and unlike the other three its advisory row names only the Application component, not the Appliance (Dell PSIRT, 2026-08-31).
CVE-2026-80238 (9.3) is the local half. Dell states that "a low-privileged operator with SSH access to the SCG host can gain root-level access to the host without requiring a password by leveraging the exposed Docker socket", and that an attacker who compromises any service inside the orchestrator container "can access the same socket and escape the container boundary to obtain host-level control" (Dell PSIRT, 2026-08-31). The gateway's own container boundary therefore provides no isolation, which matters because the unauthenticated remote paths above land inside it. Dell's advisory records its workarounds as None: Application versions before 5.36.00.00 and Appliance versions before 5.36.00.16 are affected, and upgrading to those releases is the only control the vendor offers. Germany's BSI CERT-Bund relayed the same bulletin as WID-SEC-2026-3184 on 2026-09-03 (BSI CERT-Bund, 2026-09-03). Neither Dell nor any secondary source reports exploitation or a public proof-of-concept; every issue was privately reported.
Triage: Secure Connect Gateway legitimately opens outbound sessions to Dell and legitimately performs privileged collection across the estate, so outbound connections and broad read access from the SCG host are normal and are not the signal. What separates abuse is direction and origin: an inbound request to the gateway's API from a source that is neither an administrator workstation nor the Dell support path, an administrative token in use from an address the operator team does not recognise, or container-runtime commands issued from an interactive SSH session rather than from the gateway's own orchestration.
This vulnerability is considered critical as an unauthenticated attacker can repeatedly reuse a captured request to generate ADMIN access and refresh tokens. Since there is no nonce validation or time limit on requests, the attack can be performed indefinitely.
a low-privileged operator with SSH access to the SCG host can gain root-level access to the host without requiring a password by leveraging the exposed Docker socket. Additionally, an attacker who compromises a service running within the orchestrator container can access the same socket and escape the container boundary to obtain host-level control.
it allows an attacker to execute commands remotely on a target system by sending a specially crafted request to the application, bypassing intended restrictions on code execution.