CVE-2020-37170 Overview
CVE-2020-37170 affects TapinRadio 2.12.3, a Windows internet radio client developed by Raimersoft. The vulnerability exists in the application's proxy address configuration field. A local attacker can supply 3000 bytes of arbitrary data to the address field to crash the application. The flaw is classified under CWE-120: Buffer Copy without Checking Size of Input, commonly known as a classic buffer overflow condition. Successful exploitation results in a denial of service that prevents normal program functionality until the application is restarted.
Critical Impact
Local attackers with access to the TapinRadio interface can crash the application by overwriting the proxy address field, disrupting availability of the radio client.
Affected Products
- Raimersoft TapinRadio 2.12.3
- TapinRadio for Windows (proxy configuration component)
- Raimersoft TapinRadio prior versions sharing the vulnerable address handling logic
Discovery Timeline
- 2026-02-07 - CVE-2020-37170 published to NVD
- 2026-02-19 - Last updated in NVD database
Technical Details for CVE-2020-37170
Vulnerability Analysis
The vulnerability resides in how TapinRadio 2.12.3 handles user-supplied input within its proxy address configuration field. The application accepts an oversized string of 3000 bytes without enforcing a length boundary on the destination buffer. When this oversized input is processed, the resulting memory corruption causes the application to terminate unexpectedly. The flaw is local in nature, requiring an attacker to interact with the configuration UI of the running application. While the impact is limited to availability, repeated exploitation prevents legitimate use of the radio client and may interrupt scheduled recording or streaming workflows.
Root Cause
The root cause is improper input validation in the proxy address field, mapped to CWE-120. The application does not verify the length of input before copying it into a fixed-size buffer. When the 3000-byte payload exceeds the allocated buffer, adjacent memory is overwritten and the process state becomes inconsistent, leading to a crash.
Attack Vector
Exploitation requires local access to the TapinRadio user interface and user interaction with the proxy configuration dialog. An attacker enters or pastes 3000 bytes of arbitrary data into the proxy address field and submits the configuration. The application crashes immediately upon processing the input. No network access or elevated privileges are required. Refer to the Vulncheck Denial of Service Advisory and Exploit-DB #48011 for documented reproduction details.
The vulnerability mechanism is straightforward: a long string written into the proxy address input field exceeds the buffer reserved for the value, corrupting application memory and terminating the process. No verified exploit code is reproduced here; consult the linked Exploit-DB entry for the original proof of concept.
Detection Methods for CVE-2020-37170
Indicators of Compromise
- Unexpected termination of the TapinRadio.exe process on Windows hosts
- Windows Application Event Log entries showing application crash events sourced from TapinRadio
- User reports of TapinRadio repeatedly failing immediately after opening proxy or network settings
- Modified TapinRadio configuration files containing oversized strings in proxy address fields
Detection Strategies
- Monitor endpoint telemetry for abnormal exit codes or crash dumps associated with TapinRadio.exe
- Inspect TapinRadio configuration storage for proxy address values exceeding expected length (typical hostnames are under 255 characters)
- Correlate process termination events with recent user activity in configuration dialogs
Monitoring Recommendations
- Enable Windows Error Reporting collection for TapinRadio crash artifacts and review for anomalous payload sizes
- Track installations of TapinRadio across the environment and flag versions at or below 2.12.3
- Alert on repeated crash-restart cycles of the application on the same endpoint within a short interval
How to Mitigate CVE-2020-37170
Immediate Actions Required
- Update TapinRadio to a vendor-supplied release later than 2.12.3 that addresses the proxy field input validation issue
- Restrict local user access to systems running TapinRadio where uninterrupted operation is required
- Remove or disable TapinRadio installations on shared workstations where the client is not business-essential
- Audit existing TapinRadio configurations for unusually long proxy address entries and reset them to known-good values
Patch Information
No vendor advisory URL is published in the NVD record. Users should consult the Raimersoft product page for the latest TapinRadio release and apply any update that supersedes version 2.12.3. The Vulncheck advisory provides additional context on remediation status.
Workarounds
- Avoid entering untrusted or oversized values in the TapinRadio proxy address configuration field
- Apply file system permissions on TapinRadio configuration files to limit modification to authorized users
- Use application allowlisting to restrict who can launch and configure TapinRadio on shared systems
- Maintain a backup of a known-good TapinRadio configuration to restore quickly after a crash
# Example: enumerate installed TapinRadio version on Windows endpoints via PowerShell
Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object { $_.DisplayName -like "*TapinRadio*" } |
Select-Object DisplayName, DisplayVersion, Publisher
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

