Command execution via crafted .ping.pid file
Published Dec 30, 2025 · Updated Dec 30, 2025
Command injection in affected SOUND4 appliance firmware allows remote attackers to execute operating-system commands through ping.php. The script processes a .ping.pid file in /tmp as commands, then deletes that file after the single HTTP POST request triggers it. Exploitation first requires a local authenticated user to place the specially named command file; the remote trigger itself requires no authentication.
Summary
What happened
Command injection in affected SOUND4 appliance firmware allows remote attackers to execute operating-system commands through ping.php. The script processes a .ping.pid file in /tmp as commands, then deletes that file after the single HTTP POST request triggers it. Exploitation first requires a local authenticated user to place the specially named command file; the remote trigger itself requires no authentication.
The record
- CVE
- CVE-2022-50791
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- Kantar Media
- Product
- IMPACT / PULSE / FIRST
- Classifications
- CWE-78, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Version 2: 1.1/2.15
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- sound4_ping_cmdinj.txtproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo