Menu

Star on GitHub · 3.2k

CVE-2025-47416

A vulnerability exists in the ConsoleFindCommandMatchList function in libsymproc.

Published Sep 9, 2025CWE-697EPSS 0.37%

Overview

CVE-2025-47416 is a known-severity vulnerability. It was published on September 9, 2025.

Technical description

A vulnerability exists in the ConsoleFindCommandMatchList function in libsymproc. so imported by ctpd that may lead to unauthorized execution of an attacker-defined file that gets prioritized by the ConsoleFindCommandMatchList.

A third-party researcher discovered that the ConsoleFindCommandMatchList enumerates the /dev/shm/symproc/c directory in alphabetical order to identify console commands. Permission levels are inferred from the integer values present in each command's file name. 

Confirmed Affected Hardware: TSW-760, TSW-1060

Confirmed Affected Firmware: 3.002.1061 

Fixed Firmware: no fixed released (product is discontinued and end of life)

For x70  

The Affected Firmware:- 3.000.0110.001  and versions below

The Fixed Firmware:- 3.001.0031.001

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-47416?

CVE-2025-47416 is a known-severity vulnerability. It was published on September 9, 2025.

How severe is CVE-2025-47416?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-47416?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-47416?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-47416 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.