CVE-2017-2867

CVE-2017-2867 is a critical-severity vulnerability in Natus Xltek Neuroworks with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-787.

Key facts

Description

An exploitable code execution vulnerability exists in the SavePatientMontage functionality of Natus Xltek NeuroWorks 8. A specially crafted network packet can cause a stack buffer overflow resulting in code execution. An attacker can a malicious packet to trigger this vulnerability.

Frequently asked questions

What is CVE-2017-2867?
An exploitable code execution vulnerability exists in the SavePatientMontage functionality of Natus Xltek NeuroWorks 8. A specially crafted network packet can cause a stack buffer overflow resulting in code execution. An attacker can a malicious packet to trigger this vulnerability.
How severe is CVE-2017-2867?
CVE-2017-2867 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-2867 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-2867?
CVE-2017-2867 affects Natus Xltek Neuroworks. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-2867?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-2867 published?
CVE-2017-2867 was published on 2018-04-05 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Natus Xltek Neuroworks

All CVEs affecting Natus Xltek Neuroworks →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →