/

CVE-2026-52481

Severity:

HIGH RISK

(7.5)

Information Disclosure (CWE-200) in SJRC F11 Firmware

CVE-2026-52481

Deferred

Vulnerability type

Category:

Information Disclosure

CWE:

CWE-200

Impact:

Exposure of Sensitive Information

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

A vulnerability in the tcp_actions() function of SJRC F11 SJ-GPS-PRO firmware build 2019-09-17 may allow a remote attacker to retrieve sensitive information. The issue becomes risky when the device exposes the affected network service and accepts attacker-controlled requests without sufficient authorization or filtering.

Affected context

The vulnerability occurs in the network-facing tcp_actions() functionality of SJRC F11 SJ-GPS-PRO firmware. It is most relevant to deployments using the affected firmware build where the device's TCP service is reachable by an untrusted or insufficiently trusted remote party.

Exploit preconditions

  • Attack surface: Network-accessible TCP functionality associated with tcp_actions()
  • Required access: Remote network connectivity to the affected device or service
  • Trigger point: Processing of attacker-controlled requests by tcp_actions()
  • Why exploitation is possible: The function may disclose sensitive information without adequately restricting access or controlling the data returned

Why this happens

The underlying issue is an information exposure flaw in a remotely reachable device function. The affected processing path may return sensitive data to a requester without sufficient authorization, access control, or response filtering. This behavior maps to CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where information intended for trusted users or internal operations becomes available to an unauthorized party.

Potential impact

  • An attacker could obtain sensitive device or operational information
  • Exposed data may support further attacks against the device or connected systems
  • Privacy, safety, or fleet-management risks could increase depending on the information disclosed
  • The vulnerability may assist reconnaissance and targeted follow-on activity

General mitigation guidance

Mitigation generally focuses on reducing exposure of the affected network service and ensuring that sensitive responses are available only to authorized requesters.

Common defensive patterns include:

  • Enforcing authentication and authorization before processing sensitive actions
  • Returning only the minimum information required for legitimate operations
  • Validating and filtering requests handled by network-facing functions
  • Restricting device services to trusted networks through segmentation and firewall policy
  • Removing sensitive values from diagnostic or operational responses where they are not essential
  • Applying least-privilege access controls and secure-by-default network configurations

How teams detect issues like this

Organizations can look for this issue through:

  • Static analysis and code review of network handlers that return device or operational data
  • Review signals showing missing authentication, authorization, or response filtering around tcp_actions()-like functions
  • Network monitoring for unexpected requests and responses involving the affected TCP service
  • Detection rules for devices exposing management or diagnostic services beyond trusted network boundaries
  • Automated security review tools that identify sensitive data returned from unauthenticated network paths

Sources

SourceLink
github.comgithub.com/AshtonKopelevich/SJ-GPS-PRO-F11-Vulnerability

Frequently asked

questions

Yes, exploitation may be possible remotely when the affected TCP functionality is reachable and processes requests from an untrusted source.

The available description does not establish an authentication requirement. Network reachability and any controls protecting tcp_actions() determine the practical access requirements.

Restrict access to the affected service, enforce authentication and authorization, and ensure responses disclose only the minimum necessary information.

Review all network-facing handlers for authorization and data-minimization failures, segment device networks, and monitor exposed services for unexpected access.

Find out what's already
exploitable in your codebase.