/

CVE-2026-53985

Severity:

HIGH RISK

(7.5)

Missing Authentication (CWE-306) in Ground Station

CVE-2026-53985

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthenticated Denial of Service

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Ground Station versions before 0.6.0 expose a Socket.IO service-control endpoint without authentication, allowing an unauthenticated network peer to terminate the ground-station process with a single command. Successful disruption can stop satellite tracking, SDR recording, signal processing, and rotator-control services; repeated requests may sustain the outage.

Affected context

The vulnerability occurs when the Ground Station Socket.IO server is reachable on port 7000 while authentication enforcement is disabled. A wildcard CORS policy may broaden browser-based access, but direct network reachability to the Socket.IO service remains the central condition. The affected service-control handler processes restart requests without first verifying the caller's identity or authorization.

Exploit preconditions

  • Attack surface: Socket.IO service-control interface exposed on port 7000
  • Required access: Network connectivity to the server; no credentials are required when authentication enforcement is disabled
  • Trigger point: The service_control event handler processing a restart_service command
  • Why exploitation is possible: The handler accepts a process-termination request without authentication or authorization checks
  • Persistence factor: In Docker deployments, repeated requests may repeatedly terminate the process and maintain the denial of service

Why this happens

The underlying flaw is a missing authentication and authorization check on a state-changing service-control event. The server treats a network-supplied restart request as trusted even though the caller has not been identified or granted permission to control the process. This behavior maps to CWE-306, Missing Authentication for Critical Function, because a critical operational function is available without an effective authentication gate.

Potential impact

  • An unauthenticated network peer may terminate the ground-station process
  • Active satellite-tracking sessions may be interrupted
  • SDR recording pipelines may stop unexpectedly
  • Demodulators, decoders, and rotator controllers may become unavailable
  • Repeated requests could create a persistent denial-of-service condition
  • Operators may lose telemetry, recordings, or tracking continuity

General mitigation guidance

Mitigation generally focuses on protecting operational control events behind

strong identity and authorization boundaries.

Common defensive patterns include:

  • Require authentication and explicit authorization before processing service-control events
  • Apply deny-by-default access controls to administrative Socket.IO namespaces and events
  • Restrict port 7000 exposure to trusted management networks or private service interfaces
  • Replace wildcard CORS settings with narrowly defined, trusted origins where browser access is required
  • Validate event names and command parameters against an allowlist
  • Run the service with least privilege and isolate control-plane processes from tracking workloads
  • Add rate limiting, connection controls, and supervised restart behavior to reduce repeated disruption

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and code review checks for event handlers that invoke shutdown or restart operations without authentication calls
  • Review of Socket.IO middleware, namespace guards, and per-event authorization logic
  • Searches for wildcard CORS configuration on administrative or operational interfaces
  • Integration tests confirming unauthenticated clients cannot invoke state-changing events
  • Network policy and firewall reviews verifying that control ports are not broadly exposed
  • Runtime monitoring for repeated connections and service_control or restart_service events
  • Automated security review tools that flag missing access-control checks on critical functions

Sources

SourceLink
github.comgithub.com/sgoudelis/ground-station
github.comgithub.com/sgoudelis/ground-station/commit/2ecde82a8814cbea18883ce023bf45cbf06172eb
github.comgithub.com/sgoudelis/ground-station/security/advisories/GHSA-mjp8-x6h7-229q

Frequently asked

questions

Yes. Any network peer that can reach the exposed Socket.IO server may be able to

trigger the affected event without credentials.

No, when authentication enforcement remains disabled. Network reachability to

the service is the key prerequisite.

Require authentication and authorization for every service-control event, and

restrict the control interface to trusted management networks.

Treat operational event handlers as privileged APIs, use deny-by-default

access controls, avoid broad CORS policies, and test unauthenticated access

paths in CI and deployment reviews.

Find out what's already
exploitable in your codebase.