Security readout for executives and security teams
Plain-English summary
A network-reachable flaw in Keysight IxChariot Endpoint can let an unauthenticated attacker crash the service and may permit arbitrary code execution. Successful exploitation could disrupt testing operations or compromise the endpoint host. The supplied description identifies releases before 9.5.102 as vulnerable.
Executive priority
Treat as an urgent remediation item for reachable or operationally important endpoints. Prioritize internet-accessible and cross-segment installations because exploitation needs neither credentials nor user action. Lower-isolation systems should remain restricted until their versions and vendor-supported remediation status are confirmed.
Technical view
CVE-2017-20242 is a stack-based buffer overflow, classified as CWE-121. A specially crafted network packet can trigger memory corruption without authentication or user interaction. The supplied CVSS 3.1 score is 9.8, reflecting potential confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where IxChariot Endpoint versions earlier than 9.5.102 accept traffic from untrusted or broadly accessible networks. The bundle does not identify affected ports, configurations, or deployment prevalence. Its structured version entry is ambiguous, so installed versions should be verified directly.
Exploitation context
The vulnerability is remotely reachable, requires no privileges or user interaction, and has low stated attack complexity. Crashing is confirmed as an outcome; code execution is described as potential. The bundle reports that this CVE is not in CISA KEV and provides no evidence of active exploitation.
Researcher notes
The supplied affected-version array contains “9.5.102” and “0,” while the narrative says versions before 9.5.102 are affected. Treat the narrative boundary as provisional and reconcile it with Keysight’s advisory. No packet format, affected service details, exploit evidence, or confirmed code-execution case is provided.
Mitigation direction
- Identify and prioritize all IxChariot Endpoint installations earlier than 9.5.102.
- Consult the Keysight advisory and move affected endpoints to the vendor-recommended release.
- Restrict endpoint access to trusted management and testing networks until remediation is complete.
- Monitor exposed hosts for unexpected endpoint crashes or suspicious process behavior.
Validation and detection
- Inventory IxChariot Endpoint versions and confirm whether each installation predates 9.5.102.
- Review firewall and network paths to determine whether untrusted systems can reach each endpoint.
- Confirm remediation against the Keysight advisory and document the installed replacement version.
- Check endpoint and host telemetry for unexplained crashes around network activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-20242 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9cisa-cgCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——cisa-cgVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- urlCVE reference, cisa-cg · third-party-advisory
- urlCVE reference, cisa-cg · vdb-entry
- urlCVE reference, cisa-cg · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.