Skip to content

Security Test: Crashing Page

Description

Default Severity:

When a page crashes due to an unhandled JavaScript error, it happens because the code doesn't cover all the unexpected issues that might come up during runtime. This can make the browser abruptly stop running scripts, which not only spoils the user experience but also makes the application unstable and potentially opens the door for more serious risks like data corruption or denial of service. Developers often miss handling scenarios like unusual inputs or network hiccups, leading to these crashes. If this problem is ignored, the resulting instability might allow attackers to take advantage of the system's unpredictable state.

Configuration

Identifier: configuration/crashing_page

Examples

All configuration available:

checks:
  configuration/crashing_page:
    skip: false # default

Compliance and Standards

Standard Value
OWASP API Top 10 API8:2023
OWASP LLM Top 10 LLM04:2023
PCI DSS 6.5.5
GDPR Article-32
SOC2 CC7
PSD2 Article-95
ISO 27001 A.14.2
NIST SP800-53
FedRAMP SI-11
CWE 116
CVSS Vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H