ClashMi through 1.0.32.1801 Disabled TLS Certificate Validation Enables Update MITM
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ClashMi, a proxy client application for Windows, is affected. Because it turns off TLS certificate checks in its update mechanism, an attacker positioned on the network path, such as someone running the user's proxy node, could impersonate the update server and deliver a malicious installer that runs arbitrary code on the user's computer.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
KaringX ClashMi through 1.0.32.1801 disables TLS certificate validation by default in the HttpUtils helper, allowing attackers to intercept HTTPS traffic by presenting any certificate. Attackers operating the user's proxy node can serve a forged update manifest omitting sha256 to deliver a malicious installer, achieving code execution when the update runs.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- KaringX clashmi
through 1.0.32.1801