Summary
FUXA through version 1.3.3 contains a missing authentication check in the DAQ_QUERY Socket.IO event. An unauthenticated remote attacker may query historical sensor data when the event handler does not verify the connection token, including in deployments where secure mode is enabled.
Affected context
The issue occurs in FUXA deployments that expose the Socket.IO interface and enable secure authentication controls. Although several sensitive events call isSocketAdminAuthorized, the DAQ_QUERY handler in server/runtime/index.js may process requests without performing the same authorization check.
Exploit preconditions
- Attack surface: FUXA's remotely reachable Socket.IO interface
- Required access: Network connectivity to the FUXA service; no valid authentication token may be required for the affected event
- Trigger point: A request handled by the
DAQ_QUERYSocket.IO event - Why exploitation is possible: The event handler lacks the authorization check applied to other sensitive Socket.IO events, allowing unauthenticated requests to reach historical sensor data queries
Why this happens
The vulnerability is caused by an inconsistent authorization design in which one sensitive event omits the authentication enforcement applied elsewhere.
When DAQ_QUERY processes requests without calling the central authorization routine, the presence of secureEnabled=true does not protect that event. This behavior maps to CWE-306: Missing Authentication for Critical Function, because a security-sensitive operation can be invoked without verifying the requester's identity.
Potential impact
- Unauthenticated users may access historical sensor data
- Confidentiality of operational or industrial telemetry may be reduced
- Exposed data could support reconnaissance or targeted attacks
- Organizations may face privacy, compliance, or monitoring-related consequences
General mitigation guidance
Mitigation generally focuses on enforcing authentication and authorization consistently across every sensitive Socket.IO event.
Common defensive patterns include:
- Applying a centralized authorization guard to
DAQ_QUERYand comparable data-access handlers - Failing closed when authentication state, connection tokens, or authorization decisions are absent
- Treating secure-mode configuration as a platform-wide policy rather than an event-specific option
- Restricting access to Socket.IO endpoints through network segmentation and least-privilege service exposure
- Limiting returned telemetry according to user, role, tenant, and data-retention boundaries
- Using shared middleware or policy enforcement to reduce differences between event handlers
How teams detect issues like this
Organizations can look for missing authentication controls through:
- Static analysis and code review checks for sensitive Socket.IO handlers that lack shared authorization middleware
- Searches for event registrations that access historical, device, or host data without token validation
- Tests that invoke every sensitive event with no token, an invalid token, and a low-privilege identity
- Runtime monitoring for unauthenticated DAQ_QUERY requests and unusual historical-data query volumes
- Policy checks requiring authentication guards on all data-access and administrative event routes
Automated security review tools may help identify inconsistent authorization patterns, but findings should be validated against deployment-specific access controls.

