CVE-2018-25367: NASA openVSP 3.16.1 Denial of Service via Buffer Overflow
NASA openVSP 3.16.1 contains a buffer overflow vulnerability that allows local attackers to crash the application by supplying an excessively long string in the geometry name field. Attackers can trigger a denial of service by pasting a 5000-byte payload into the name input field within the Geom browser pod addition interface.
Security readout for executives and security teams
Plain-English summary
CVE-2018-25367 affects NASA openVSP 3.16.1. A local attacker can crash the application by entering an excessively long geometry name. The documented impact is denial of service to the desktop application, not system compromise. There is no KEV listing or source evidence of active exploitation.
Executive priority
Treat this as a moderate workstation application risk. It is unlikely to justify emergency response unless openVSP 3.16.1 supports critical engineering work, but it should be inventoried and remediated through normal vulnerability management once vendor guidance is confirmed.
Technical view
The issue is a CWE-120 buffer overflow in openVSP 3.16.1 triggered through the geometry name field in the Geom browser pod addition interface. The CVSS 4.0 score is 6.9 with local attack vector and high vulnerable-system availability impact. Sources do not identify a patch commit or fixed version.
Likely exposure
Exposure is most likely on engineering or research workstations running NASA openVSP 3.16.1. Business impact is localized application interruption and potential workflow disruption. The bundle does not support broader product, server-side, or remote internet exposure claims.
Exploitation context
A public ExploitDB reference exists, but KEV is false and the bundle does not show active exploitation. The described attack requires local interaction with the application input path and causes a crash rather than documented code execution.
Researcher notes
Evidence supports local denial of service via buffer overflow in openVSP 3.16.1. The bundle does not establish active exploitation, remote reachability, privilege escalation, data compromise, code execution, patch status, or affected versions beyond 3.16.1.
Mitigation direction
Inventory openVSP installations and identify any running version 3.16.1.
Check NASA OpenVSP release notes or advisories for vendor guidance and fixed versions.
Limit openVSP 3.16.1 use to trusted users and managed workstations.
Avoid relying on vulnerable versions for time-sensitive operational workflows.
Prioritize upgrade or replacement if vendor guidance confirms a fixed release.
Validation and detection
Confirm installed openVSP versions on engineering and research endpoints.
Review endpoint crash telemetry for repeated openVSP crashes around geometry editing.
Verify whether vulnerable systems are accessible only to trusted local users.
Track NASA OpenVSP and CVE sources for any published remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-120: 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.