/

CVE-2026-38057

Severity:

HIGH RISK

(8.1)

CSRF (CWE-352) on Reboot API in iDirect iQ200 Modem

CVE-2026-38057

Awaiting Analysis

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Denial of Service via Forced Device Reboot

Severity:

HIGH RISK

(8.1)

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

The iDirect iQ200 exposes a state-changing reboot API that does not validate CSRF tokens and relies only on a session cookie without SameSite protection.

An attacker can abuse a victim administrator's authenticated browser to trigger cross-site POST requests, causing unexpected device reboots and potential satellite link loss.

Affected context

This vulnerability manifests in deployments where administrators manage the iDirect iQ200 through a web interface that maintains session state using cookies.

The issue is present when:

  • The /api/reboot endpoint accepts authenticated POST requests without CSRF validation
  • Session cookies are sent cross-site because they lack the SameSite attribute
  • Administrators browse untrusted websites while logged in to the device management console

Exploit preconditions

  • Attack surface: Browser-based management interface for the iDirect iQ200
  • Required access: Ability to lure an authenticated administrator to a malicious web page (e.g., via link, iframe, or embedded script)
  • Trigger point: The victim's browser automatically submits a crafted POST request to /api/reboot while the session cookie is still valid
  • Why exploitation is possible: The reboot endpoint does not enforce CSRF defenses, and cookies without SameSite allow cross-site requests to be authenticated implicitly

Why this happens

The underlying bug is a missing cross-site request forgery protection on a sensitive, state-changing API endpoint.

The reboot action is bound solely to the presence of an authenticated session cookie, without verifying a per-request CSRF token or other origin-based assurances.

This corresponds to CWE-352, where the application implicitly trusts browser-supplied credentials on cross-origin requests and fails to distinguish user-intended actions from attacker-forced submissions.

Potential impact

  • Forced reboot of the iQ200 device without administrator consent
  • Temporary loss of satellite link connectivity and service interruption
  • Sustained denial-of-service through repeated CSRF-triggered reboots
  • Disruption of downstream systems and applications relying on the modem's connectivity
  • Potential operational and business impact due to unreliable network availability

General mitigation guidance

Effective mitigation centers on treating state-changing endpoints as high-risk and enforcing robust request authenticity checks.

Common defensive patterns include:

  • Requiring server-side validated CSRF tokens or equivalent anti-CSRF mechanisms for all state-changing POST, PUT, and DELETE requests
  • Applying SameSite attributes to session cookies (e.g., Lax or Strict) to reduce the automatic inclusion of cookies in cross-site requests
  • Using additional signals such as Origin and Referer validation for sensitive actions, while accounting for privacy and network variations
  • Introducing explicit confirmation flows or administrative action gates for critical operations like device reboot
  • Applying least-privilege principles so only necessary accounts can invoke high-impact device operations

How teams detect issues like this

Detection typically involves combining code-level review with behavioral testing of the web interface.

Useful approaches include:

  • Static analysis rules or secure coding checklists that flag state-changing endpoints lacking CSRF token validation
  • Manual code review to ensure all authenticated POST routes check anti-CSRF mechanisms and do not rely solely on cookies
  • Security testing using crafted HTML forms or scripts to confirm whether cross-origin POSTs with valid cookies can trigger sensitive actions
  • Policy-based enforcement in CI/CD to block deployments where critical administrative APIs are missing CSRF protections or where cookies lack appropriate SameSite attributes

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-183-01.json
support.idirect.netsupport.idirect.net/s/login
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-183-01

Frequently asked

questions

Yes. A remote attacker can exploit it indirectly by hosting a malicious page and causing an authenticated administrator's browser to send a forged POST request to the device.

The attacker does not need direct access to the device. They need the ability to entice an already authenticated administrator to visit or interact with attacker-controlled content while logged into the iQ200 interface.

The safest pattern is to require robust CSRF protection on all state-changing endpoints, validate per-request authenticity (e.g., CSRF tokens plus origin checks), and avoid relying solely on cookies for authorization.

Adopt a default security posture where every state-changing HTTP operation must pass explicit anti-CSRF checks, configure cookies with restrictive SameSite attributes, and include CSRF requirements in secure coding standards and automated review pipelines.

Find out what's already
exploitable in your codebase.