Progress Software Progress® Telerik® Fiddler® Classic
Weak Executable Signature Verification Vulnerability in Progress® Telerik® Fiddler® Classic
In Progress® Telerik® Fiddler® Classic for Windows, versions prior to v6.0.20262.10021, the integrity check applied to the external helper tools launched by the application is insufficient. Before executing a helper tool, the application only verifies that the file carries a valid Authenticode signature whose certificate subject name matches a broad allow list of publisher name fragments, rather than verifying that the file is the specific executable shipped with that version of the product. A local threat actor with low privileges who replaces one of these helper executables with any other validly signed binary from an allow-listed publisher can cause the substituted binary to be executed by the application, including with Administrator privileges for the tools that request elevation, resulting in privilege escalation and execution of unintended code. Successful exploitation requires the user to launch the affected external tool and to approve the elevation prompt without noticing that it refers to a different executable.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.0.0, < 6.0.20262.10021
Fixed in 6.0.20262.10021
Mitigation
Upgrade Progress® Telerik® Fiddler® Classic to 6.0.20262.10021 or later.
Workaround
Carefully review every User Account Control elevation prompt raised by Fiddler Classic and confirm that it refers to the expected executable before approving it. Alternatively, avoid launching external tools from the Fiddler Classic application, such as the Windows 8 Loopback Exemptions tool or the machine store certificate trust tool.
References
- Vendor advisory docs.telerik.com/fiddler/knowledge-base/kb-security-…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.