CVE-2017-15643 json
An active network attacker (MiTM) can achieve remote code execution on a machine that runs IKARUS Anti Virus 2.16.7.
published 2017-10-19 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-7094
- cvss
- 7.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.4%
- EPSS 6.4% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
An active network attacker (MiTM) can achieve remote code execution on a machine that runs IKARUS Anti Virus 2.16.7. IKARUS AV for Windows uses cleartext HTTP for updates along with a CRC32 checksum and an update value for verification of the downloaded files. The attacker first forces the client to initiate an update transaction by modifying an update field within an HTTP 200 response, so that it refers to a nonexistent update. The attacker then modifies the HTTP 404 response so that it specifies a successfully found update, with a Trojan horse executable file (e.g., guardxup.exe) and the correct CRC32 checksum for that file.
Timeline
- First public exploit (EDB-44055)
- Published
Exploit prediction
6.39% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44055 Ikraus Anti Virus 2.16.7 - Remote Code Execution remote, 2017-10-16
- blogs.securiteam.com https://blogs.securiteam.com/index.php/archives/3485 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.4 | CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.6 | AV:N/AC:H/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-444 Inconsistent Interpretation of HTTP Requests
References
-
blogs.securiteam.com
/index.php/archives/3485
exploit, technical-description, third-party-advisory
-
ikarussecurity.com
/about-ikarus/security-blog/vulnerability-in-windows-antivirus-products-ik-sa-2017-0001/
vendor-advisory
Sources
- CVE List CVE-2017-15643
- NVD CVE-2017-15643
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.