# CVE-2017-15643: Code injection in n/a

> A man-in-the-middle attacker can achieve remote code execution on Windows machines running IKARUS Anti Virus by intercepting and modifying cleartext HTTP update traffic.

- **Severity:** High 7.4 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-68qc-x6c7-f66c

## What is CVE-2017-15643?

CVE-2017-15643 is a high-severity code injection vulnerability in n/a, published on 19 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2017-15643?

It affects 1 product.


Products: Ikarussecurity Ikarus Antivirus.

## How do I fix CVE-2017-15643?

No fix has been published for CVE-2017-15643 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-15643 being exploited?

There is no known exploitation of CVE-2017-15643 in the wild and no public exploit code.

Public exploit code:

- Ikraus Anti Virus 2.16.7 - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15643 and fix it if it is affected.

What it is: CVE-2017-15643 is a high-severity code injection vulnerability in n/a, published on 19 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15643 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-15643/ (Markdown: https://insights.sbomify.com/CVE-2017-15643/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-15643
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-15643
- OSV: https://osv.dev/vulnerability/CVE-2017-15643

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-15643/
Summaries are generated and may contain mistakes; the official description above is the record.