← Advisories

SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x (upload.cgi) Unauthenticated Remote Code Execution

Critical
Advisory ID
ZSL-2022-5741
Release Date
14 December 2022
Affected Version
FM/HD Radio Processing:, Impact/Pulse/First (Version 2: 1.1/2.15), Impact/Pulse/First (Version 1: 2.1/1.69), Impact/Pulse Eco 1.16, Voice Processing:, BigVoice4 1.2, BigVoice2 1.30, Web-Audio Streaming:, Stream 1.1/2.4.29, Watermarking:, WM2 (Kantar Media) 1.11
Tested On
Apache/2.4.25 (Unix), OpenSSL/1.0.2k, PHP/7.1.1, GNU/Linux 5.10.43 (armv7l), GNU/Linux 4.9.228 (armv7l)
Summary

The SOUND4 IMPACT introduces an innovative process - mono and stereo parts of the signal are processed separately to obtain perfect consistency in terms of both sound and level. Therefore, in moving reception, when the FM receiver switches from stereo to mono and back to stereo, the sound variations and changes in level are reduced by over 90%. In the SOUND4 IMPACT processing chain, the stereo expander can be used substantially without any limitations.

With its advanced functionalities and impressive versatility, SOUND4 PULSE gives clients the ultimate price - performance ratio, providing much more than just a processor. Flexible and powerful, it ensures perfect sound quality and full compatibility with radio broadcasting standards and can be used simultaneously for FM and HD, DAB, DRM or streaming.

SOUND4 FIRST provides all the most important functionalities you need in an FM/HD processor and sets the bar high both in terms of performance and affordability. Designed to deliver a sound of uncompromising quality, this tool gives you 2-band processing, a digital stereo generator and an IMPACT Clipper

Description

SOUND4 products suffer from an unauthenticated remote code execution vulnerability. An attacker can exploit this vulnerability by abusing the firmware upgrade/upload functionality, which contains a path traversal flaw. This allows the attacker to arbitrarily write a malicious file to a location on the system with www-data permissions, which can be executed to gain unauthorized access.

Proof of Concept
Disclosure Timeline
26.09.2022Vulnerability discovered.
30.09.2022Vendor contacted.
13.12.2022No response from the vendor.
14.12.2022Public security advisory released.
Credits
Vulnerability discovered by Gjoko Krstic
References
Changelog
14.12.2022Initial release
28.12.2022Added reference [1] and [2]
20.04.2023Added reference [3]
24.03.2026Added reference [4]