# CVE-2017-20242: Keysight IxChariot Endpoint stack-based buffer overflow

> Unauthenticated remote attackers can trigger a stack-based buffer overflow in Keysight IxChariot Endpoint to execute arbitrary code or cause a denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-qpw6-pm56-6c3g

## What is CVE-2017-20242?

CVE-2017-20242 is a critical memory corruption vulnerability in Keysight IxChariot, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Keysight IxChariot Endpoint before 9.5.102 contains a stack-based buffer overflow. An unauthenticated remote attacker can send a specially crafted packet to crash the endpoint or potentially execute arbitrary code.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2017-20242 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20242 is a critical memory corruption vulnerability in Keysight IxChariot, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-20242 in the wild and no public exploit code.

Affected product: Keysight IxChariot. 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-20242/ (Markdown: https://insights.sbomify.com/CVE-2017-20242/index.md)
```

## Sources

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

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