Reachable Assertion
A reachable assertion occurs when an attacker can trigger an assert() statement or similar debugging check, causing the application to crash or behave in a more disruptive way than intended. This turns a helpful development tool into a denial-of-service vulnerability.
Assertions are meant to catch logic errors during development, but if left in production code, they can be weaponized. An attacker who discovers the trigger condition can force the application to exit abruptly, disrupting service for all users. For instance, a single triggered assert() in a multi-connection server could terminate every active connection, causing widespread outage. While SAST tools can flag the presence of assertions, managing this risk at scale across a large codebase is challenging. An ASPM platform like Plexicus helps by continuously tracking these flaws in production, and its AI can recommend specific fixes—such as replacing the assert with proper error handling—saving significant manual remediation time.
Impact: DoS: Crash, Exit, or Restart
An attacker that can trigger an assert statement can still lead to a denial of service if the relevant code can be triggered by an attacker, and if the scope of the assert() extends beyond the attacker's own session.
Strategy: Input Validation
ID : DX-183
In the excerpt below, an AssertionError (an unchecked exception) is thrown if the user hasn't entered an email address in an HTML form.Code Example:
javaassertion failure
- The CERT Oracle Secure Coding Standard for Java (2011)
- Software Fault Patterns