Page History

Diagnostic tests can be incorporated into programs by using the assert() statement. Assertions are primarily intended for use during debugging and are generally often turned off before code is deployed by using the -disableassertions (or -da) java optionJava runtime switch. Consequently, assertions should be used to protect against incorrect programmer assumptions and not for runtime error checking.

Assertions should never be used to verify the absence of runtime (as opposed to logic) errors, such as

• invalid Invalid user input (including command-line arguments and environment variables)
• file File errors (for example, errors opening, reading, or writing files)
• network Network errors (including network protocol errors)
• outOut-of-memory conditions (when the Java Virtual Machine [JVM] cannot allocate space for a new object and the garbage collector cannot make sufficient space available)
• system System resource exhaustion (for example, out-of-file descriptors, processes, threads)
• system System call errors (for example, errors executing files, locking or unlocking mutexes)
• invalid Invalid permissions (for example, file, memory, user)

Code that protects against an inputI/output O error, for example, cannot be implemented as an assertion because it must be presented present in the deployed executable.

In particular, assertions Assertions are generally unsuitable for server programs or embedded systems in deployment. A failed assertion can lead to a denial-of-service (DoS) attack if triggered by a malicious user. In such situations, a soft failure mode, such as writing to a log file and rejecting the request, is more appropriate.

Noncompliant Code Example

This noncompliant code example uses the assert() statement to verify that input was available. Because input availability depends on the user and can become exhausted at any point during a process lifetime, a robust program must be prepared to gracefully handle and recover from its exhaustion. Therefore, using the assert() statement to verify that input was available would be inappropriate because doing so might lead to an abrupt termination of the process, opening up the possibility of a DoS attack.:

BufferedReader br;

// Set up the BufferedReader br

String line;

// ...

line = br.readLine();

assert line != null;

Because input availability depends on the user and can be exhausted at any point during program execution, a robust program must be prepared to gracefully handle and recover from the unavailability of input. However, using the assert statement to verify that some significant input was available is inappropriate because it might lead to an abrupt termination of the process, resulting in a denial of service.

Compliant Solution

This compliant solution demonstrates how the recommended way to detect and handle possible unavailability of input unavailability.:

BufferedReader br;

// Set up the BufferedReader br

String line;

// ...

line = br.readLine();

if (line == null) {
  // handleHandle error
}

Applicability

Assertions are a valuable diagnostic tool for finding and eliminating software defects that may result in vulnerabilities. The absence of assertions, however, does not mean that code is incorrectbug-free.

In general, the misuse of the assert statement for runtime checking rather than checking for logical errors cannot be detected automatically.

Automated Detection

Bibliography

...

Image Modified Image Modified Image Modified