/

CVE-2026-35064

Severity:

HIGH RISK

(7.5)

Missing Authentication in SenseLive X3050 Management

CVE-2026-35064

Analyzed

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthenticated Device Enumeration and Targeted Reconnaissance

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

SenseLive X3050's management ecosystem exposes a discovery mechanism that can be accessed without authentication, allowing enumeration of deployed units over the vendor's management protocol.

An attacker on the same network segment can identify device presence, unique identifiers, and management interfaces without credentials, enabling targeted reconnaissance and follow-on attacks.

Affected context

This vulnerability affects SenseLive X3050 deployments that use the vendor's management ecosystem and protocol for device monitoring and control.

The issue appears when the discovery functionality is implemented as a network-exposed service that responds to queries before any authentication or access control is applied.

Any environment where X3050 units share a broadcast or local network segment with untrusted devices, guest networks, or partially segmented OT/IT environments may be exposed to unauthenticated enumeration of units and management endpoints.

Exploit preconditions

  • Attack surface: Network-exposed management protocol for SenseLive X3050 units
  • Required access: Network adjacency (same L2 segment, VLAN, or routable path that can reach the management protocol endpoint)
  • Authentication: Not required for discovery; the service responds to unauthenticated requests
  • Trigger point: Sending crafted or standard discovery messages to the management protocol port or broadcast mechanism
  • Why exploitation is possible: Discovery functions are implemented at the service layer and are not gated behind authentication or access control checks, allowing unauthenticated requests to elicit valid responses containing device metadata.

Why this happens

The underlying issue matches CWE-306: Missing Authentication for Critical Function.

The management ecosystem exposes discovery capabilities—such as responding with device identifiers, type, and management interface information—without requiring authentication or verifying caller trust.

Instead of treating discovery as a privileged operation that should be limited to authorized management stations, the protocol treats it as an open service feature.

This insecure pattern allows any network-adjacent actor to invoke critical discovery behavior, turning a convenience function into a reconnaissance oracle for attackers.

Potential impact

  • Mapping of all reachable SenseLive X3050 units on a network segment
  • Identification of device-specific identifiers, models, and management interfaces that can inform targeted exploit attempts
  • Facilitated password-guessing, brute-force, or default-credential attacks by highlighting live management endpoints
  • Support for network reconnaissance and lateral movement planning within OT/IoT or mixed IT environments
  • Increased effectiveness of subsequent denial-of-service or configuration-tampering attempts against identified units

General mitigation guidance

Mitigation typically focuses on enforcing authentication around discovery functions and reducing unnecessary exposure of management protocols.

Common defensive patterns include:

  • Treating device discovery as a privileged management operation, requiring authentication or cryptographic trust (e.g., mutual authentication or pre-shared keys) before returning detailed information.
  • Limiting the information returned by unauthenticated queries to minimal, non-sensitive data or disabling unauthenticated discovery entirely.
  • Enforcing strict network segmentation to isolate management traffic onto dedicated, trusted management VLANs or out-of-band networks, preventing access from user, guest, or internet-facing segments.
  • Applying least-privilege design to management services, ensuring components expose only the minimal set of remotely-invocable operations required for secure operation.
  • Implementing rate limiting and request validation on the management protocol to reduce bulk enumeration opportunities, even for authenticated users.

How teams detect issues like this

Detection of this class of issue generally combines protocol analysis, code review, and configuration validation:

  • Reviewing management protocol specifications and implementation code to confirm that discovery or enumeration operations are protected by authentication or access control checks.
  • Using static analysis or security linters to flag network handlers that respond with device metadata prior to any authentication logic.
  • Conducting black-box testing on lab deployments by sending unauthenticated discovery requests from an unprivileged host and observing whether devices respond with identifiers or management URLs.
  • Implementing network monitoring rules (e.g., IDS/IPS signatures) to detect anomalous or bulk discovery activity, such as repeated broadcast or multicast management discovery packets from non-management hosts.
  • Incorporating security requirements into design and code review checklists to ensure new or updated protocol features never bypass authentication boundaries.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-111-12.json
senselive.iosenselive.io/contact
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-111-12

Frequently asked

questions

Typically, exploitation requires network adjacency to the SenseLive X3050 management segment. If management services are exposed over routed or internet-facing interfaces without proper segmentation, remote exploitation becomes possible, but this depends on each deployment's network design.

No. The core issue is that the discovery function responds to unauthenticated requests. Any host that can reach the management protocol interface on the network can query and enumerate devices without providing credentials.

The safest pattern is to require authentication (or strong cryptographic trust) before honoring discovery requests that return identifiable or sensitive device information, and to minimize the amount of data disclosed. Where possible, disable open discovery entirely and rely on pre-configured, authenticated management relationships.

During design, treat discovery, enumeration, and configuration endpoints as security-sensitive functions subject to the same authentication and authorization requirements as other management operations. Incorporate threat modeling for management protocols, enforce least privilege and segmentation, and use security-focused code review practices to ensure no network handler returns sensitive metadata before authentication.

Find out what's already
exploitable in your codebase.