HIGH 8.1

CVE-2026-38057: iDirect iQ200 CSRF Vulnerability Enables Remote Reboot & DoS

The iDirect iQ200 satellite communication device is vulnerable to cross-site request forgery (CSRF) attacks on its administrative control interface. An attacker can trick an authenticated administrator into visiting a malicious webpage that silently triggers a device reboot by exploiting the lack of CSRF token validation and improper session cookie configuration. This can lead to immediate loss of satellite connectivity and, if repeated, sustained service disruption.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.1 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Weaknesses (CWE)
CWE-352
Affected products
0 configuration(s)
Published / Modified
2026-07-10 / 2026-07-10

NVD description (verbatim)

The iDirect iQ200 does not validate CSRF tokens on state-changing API endpoints after authentication. The /api/reboot endpoint accepts POST requests authenticated solely by a session cookie that lacks the SameSite attribute. A remote attacker can host a malicious web page that, when visited by an authenticated administrator, automatically submits a cross-site POST request causing an immediate device reboot and satellite link loss. Repeated attacks can sustain a denial-of-service condition.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-38057 is a CSRF vulnerability in the iDirect iQ200's REST API. The /api/reboot endpoint accepts state-changing POST requests authenticated solely via a session cookie without the SameSite attribute, and does not validate CSRF tokens. An attacker can craft a malicious page that, when loaded by an authenticated user, automatically submits a forged POST request to /api/reboot. The device lacks the controls necessary to distinguish legitimate user-initiated requests from cross-origin forgeries, enabling unauthorized administrative actions.

Business impact

Satellite communication infrastructure relying on iQ200 devices faces elevated risk of unplanned service outages. Administrators could unknowingly trigger device reboots, causing immediate satellite link loss and service interruption. For organizations operating time-sensitive satellite uplinks (maritime, aviation, remote operations), even brief outages pose operational and safety risks. Repeated exploitation can sustain a denial-of-service state, degrading availability and confidence in the network.

Affected systems

iDirect iQ200 devices are affected. The vulnerability applies to instances where administrators with active sessions access untrusted web content. Organizations should verify which endpoints and firmware versions are deployed in their environment and whether administrative users are exposed to untrusted internet content during active sessions.

Exploitability

Exploitation requires low complexity: an attacker needs only to host a malicious webpage and wait for an authenticated administrator to visit it. No special network position or user interaction beyond visiting a website is required. The CVSS score of 8.1 (HIGH) reflects the combination of network accessibility, low attack complexity, and high impact on integrity and availability. However, the attack does require the victim to be authenticated and to visit a malicious site, reducing the likelihood of opportunistic mass exploitation.

Remediation

Apply a security patch from the vendor that adds CSRF token validation to the /api/reboot and other state-changing endpoints. The patch should also ensure session cookies are set with the SameSite attribute (Strict or Lax recommended) to prevent cross-origin cookie transmission. Verify the patch version against the vendor advisory. In the interim, restrict administrative access to trusted networks and educate administrators about the risks of visiting untrusted websites during active sessions.

Patch guidance

Consult the iDirect vendor advisory for the specific patch version and deployment steps. The fix should address both CSRF token validation on /api/reboot and related endpoints, as well as session cookie configuration. Apply patches to all iQ200 devices in production, prioritizing those exposed to untrusted network access. Test patches in a non-production environment before full deployment to confirm compatibility and operational stability.

Detection guidance

Monitor API logs for POST requests to /api/reboot and other state-changing endpoints that lack valid CSRF tokens or originate from unusual referrers. Review session cookie attributes in responses to confirm SameSite is set correctly. Implement network-level monitoring to detect repeated reboot commands in short timeframes, which may indicate sustained exploitation attempts. Security teams should also audit administrative user activity logs to identify unexpected device reboots.

Why prioritize this

This vulnerability merits prioritized patching because it enables remote denial-of-service against critical satellite infrastructure with minimal attack effort. The combination of HIGH CVSS severity, lack of KEV designation (suggesting it is not yet widely exploited in the wild), and the operational criticality of satellite devices creates a narrow window for remediation before adoption by adversaries. Organizations should address this before the vulnerability matures in attacker toolkits.

Risk score, explained

CVSS 3.1 score of 8.1 (HIGH) reflects: network accessibility (AV:N), low attack complexity (AC:L), no privileges required (PR:N), requirement for user interaction (UI:R), no scope change (S:U), no confidentiality impact (C:N), high integrity impact (I:H) from arbitrary administrative actions, and high availability impact (A:H) from forced reboots. The UI:R factor moderates an otherwise critical score; however, the attack remains highly effective against targeted administrators and is straightforward to automate.

Frequently asked questions

Can an attacker reboot my iQ200 without an authenticated administrator visiting a malicious website?

No. The vulnerability requires that an authenticated administrator (with an active session cookie) visit a malicious webpage controlled by the attacker. If no administrator is logged in, or if no one visits the attacker's page, exploitation cannot occur. This requirement limits the attack surface but does not eliminate the risk, especially in environments where administrators routinely access external web content.

How is this different from a regular password compromise?

A CSRF attack does not require the attacker to know or steal the administrator's password. Instead, it abuses the administrator's existing, legitimate session to forge requests on their behalf. This makes CSRF particularly insidious because even strong passwords offer no protection—the attacker simply needs to trick the admin into visiting a malicious page while logged in.

If I patch the device, will my existing administrative sessions need to be invalidated?

The patch itself does not require session invalidation, but security best practice recommends logging out and back in after applying any security patch to ensure the new security controls are fully active. Consult the vendor's patch release notes for specific guidance on session handling.

Is this vulnerability actively being exploited in the wild?

As of the publication date, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, suggesting limited evidence of active exploitation. However, the attack is straightforward to execute, and the lack of KEV designation should not delay patching efforts—it indicates an opportunity to remediate before adversaries widely adopt the technique.

This analysis is based on information published as of July 10, 2026. Patch availability, affected versions, and remediation timelines are subject to vendor updates. Organizations should verify compatibility and test patches in non-production environments before deployment. SEC.co provides this information for risk assessment and remediation planning only; it does not constitute legal or compliance advice. Always consult official vendor advisories and internal security policies for authoritative guidance. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).