Hpe Nonstop Http Webserver
Monthly
Memory corruption in the HPE NonStop HTTP WEBSERVER can be triggered by network-delivered HTTP input, causing the web server process to fail and potentially halting the NonStop system itself (CVSS 8.2, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H). Any HPE NonStop deployment that exposes the WEBSERVER component to an untrusted network is in scope, since the assessed vector requires no authentication, privileges, or user interaction against a listening server. The practical risk is bounded by the relatively small installed base of the NonStop platform and by the fact that the worst realistic outcome is availability loss rather than code execution or data disclosure; there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis.
Memory corruption in the HPE NonStop HTTP WEBSERVER can be triggered by network-delivered HTTP input, causing the web server process to fail and potentially halting the NonStop system itself (CVSS 8.2, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H). Any HPE NonStop deployment that exposes the WEBSERVER component to an untrusted network is in scope, since the assessed vector requires no authentication, privileges, or user interaction against a listening server. The practical risk is bounded by the relatively small installed base of the NonStop platform and by the fact that the worst realistic outcome is availability loss rather than code execution or data disclosure; there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis.