ClashMi through 1.0.32.1801 Disabled TLS Certificate Validation Enables Update MITM
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| KaringX | clashmi | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Karingx | Clashmi |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.270% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Karingx
Karingx clashmi |
|
| Vendors & Products |
Karingx
Karingx clashmi |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | ClashMi through 1.0.32.1801 Disabled TLS Certificate Validation Enables Update MITM | |
| Weaknesses | CWE-295 | |
| References |
|
|
| Metrics |
cvssV3_1
|