Crucial Tinyproxy Flaw Opens Over 50,000 Hosts to Distant Code Execution

Might 06, 2024NewsroomVulnerability / Server Safety

Greater than 50% of the 90,310 hosts have been discovered exposing a Tinyproxy service on the web that is weak to a crucial unpatched safety flaw within the HTTP/HTTPS proxy device.

The problem, tracked as CVE-2023-49606, carries a CVSS rating of 9.8 out of a most of 10, per Cisco Talos, which described it as a use-after-free bug impacting variations 1.10.0 and 1.11.1, which is the most recent model.

“A specially crafted HTTP header can trigger reuse of previously freed memory, which leads to memory corruption and could lead to remote code execution,” Talos stated in an advisory final week. “An attacker needs to make an unauthenticated HTTP request to trigger this vulnerability.”

Cybersecurity

In different phrases, an unauthenticated risk actor may ship a specifically crafted HTTP Connection header to set off reminiscence corruption that may end up in distant code execution.

In keeping with knowledge shared by assault floor administration firm Censys, of the 90,310 hosts exposing a Tinyproxy service to the general public web as of Might 3, 2024, 52,000 (~57%) of them are operating a weak model of Tinyproxy.

A majority of the publicly-accessible hosts are situated within the U.S. (32,846), South Korea (18,358), China (7,808), France (5,208), and Germany (3,680).

Talos, which reported the difficulty to December 22, 2023, has additionally launched a proof-of-concept (PoC) for the flaw, describing how the difficulty with parsing HTTP Connection connections might be weaponized to set off a crash and, in some circumstances, code execution.

The maintainers of Tinyproxy, in a set of commits revamped the weekend, referred to as out Talos for sending the report back to a probable “outdated email address,” including they have been made conscious by a Debian Tinyproxy package deal maintainer on Might 5, 2024.

Cybersecurity

“No GitHub issue was filed, and nobody mentioned a vulnerability on the mentioned IRC chat,” rofl0r stated in a commit. “If the issue had been reported on Github or IRC, the bug would have been fixed within a day.”

Customers are suggested to replace to the most recent model as and once they turn into obtainable. It is also really useful that the Tinyproxy service isn’t uncovered to the general public web.

Discovered this text attention-grabbing? Observe us on Twitter and LinkedIn to learn extra unique content material we put up.

Recent articles