/

CVE-2026-38059

Severity:

HIGH RISK

(7.5)

Missing Authentication (CWE-306) in iDirect iQ200 APIs

CVE-2026-38059

Awaiting Analysis

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized Information Disclosure and Device Impersonation

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

The iDirect iQ200 exposes identity-related REST API endpoints without enforcing authentication, allowing unauthenticated network clients to query sensitive device metadata.

Under these conditions, an attacker on the same reachable network can harvest serial numbers, Device IDs, Terminal Private Key identifiers, MAC addresses, and firmware versions, which may then be used for terminal impersonation and targeted reconnaissance.

Affected context

This vulnerability appears in iDirect iQ200 deployments where the /api/identity and broader /api/ REST endpoints are reachable over the management or operational network without additional access controls.

It becomes relevant in environments where devices are exposed to shared or semi-trusted networks, or where perimeter controls do not fully shield these endpoints from untrusted clients.

The risk is heightened when the Device ID (DID) and Terminal Private Key identifier (TPK) are used as core credentials for satellite network authentication and when enumeration of firmware versions can inform targeted attacks.

Exploit preconditions

  • Attack surface: Network-accessible REST API endpoints at /api/identity and /api/
  • Required access: Unauthenticated network connectivity to the device (e.g., same LAN, WAN segment, or routed path)
  • Trigger point: Issuing HTTP requests to identity or general API endpoints without providing credentials
  • Why exploitation is possible: The service does not enforce authentication or authorization checks before returning sensitive device identifiers and configuration details

Why this happens

The root cause aligns with CWE-306: Missing Authentication for Critical Function.

Identity and configuration APIs, which expose sensitive device information and authentication artifacts, are deployed without mandatory authentication or session validation.

This design assumes implicit trust in network locality instead of enforcing strong, per-request authentication, leading to a situation where any network-capable client can query critical identifiers and metadata without restriction.

Potential impact

  • Unauthorized retrieval of serial numbers, Device IDs (DID), and Terminal Private Key identifiers (TPK)
  • Increased risk of terminal impersonation within the satellite network ecosystem
  • Facilitation of network reconnaissance, including mapping of firmware versions and device characteristics
  • Support for targeted exploitation or social engineering using detailed device intelligence
  • Contribution to broader supply-chain or infrastructure attacks if harvested identifiers are reused across systems

General mitigation guidance

Effective mitigation focuses on enforcing strong access control around device management and identity APIs and minimizing exposure of sensitive identifiers.

Common patterns include:

  • Requiring authentication and authorization checks for all identity- and configuration-related endpoints, regardless of network location
  • Applying role-based access controls so only authorized operators can see DID, TPK identifiers, and detailed device metadata
  • Reducing the amount of sensitive information returned by default and segregating high-value identifiers into separate, tightly controlled interfaces
  • Enforcing secure-by-default network configurations, such as binding management APIs only to dedicated management interfaces or VPNs
  • Designing credential and identifier usage so that static identifiers, even if disclosed, cannot be used alone for authentication

How teams detect issues like this

Organizations can detect similar missing-authentication issues by:

  • Performing network scans and API enumeration to identify endpoints returning sensitive data without requiring credentials
  • Using static or dynamic analysis tools to highlight controller methods or routes lacking authentication middleware or access checks
  • Incorporating security-focused code review checklists that flag any identity, configuration, or key-related endpoints exposed without explicit protection
  • Applying API gateway or reverse proxy policies that require authentication by default and log any exceptions or unauthenticated accesses
  • Monitoring device logs and network telemetry for repeated unauthenticated requests to identity or management APIs

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, if the iQ200 management or operational interface is reachable from an untrusted network segment, an attacker can access the exposed API endpoints remotely without prior authentication.

The attacker needs only network-level access to the device's exposed API interface; no valid credentials or prior foothold on the device are required.

The safest pattern is to enforce mandatory authentication and authorization for all identity and management endpoints, restrict which roles can retrieve sensitive identifiers, and ensure that no critical function or secret-bearing interface is accessible without robust access control.

Adopt a secure-by-default API design where all endpoints require authentication unless explicitly and narrowly justified, use centralized access control middleware, limit exposure of static identifiers, and regularly test management interfaces through security assessments and automated policy checks.

Find out what's already
exploitable in your codebase.