AD5030: EnableExceptionHandlingMachO¶

Summary¶

Description¶

Mach-O binaries should have proper exception handling enabled to ensure clean program termination and prevent undefined behavior on errors.

How It Works¶

The rule checks for exception handling infrastructure:

1. __eh_frame section presence
2. __unwind_info section
3. Exception handling symbols

Why This Matters¶

Proper exception handling ensures that errors are caught and handled correctly, preventing undefined behavior that could be exploited.

Exception Handling on Apple Platforms¶

Security Implications¶

C++ Exception Safety¶

// Good: Proper exception handling
try {
    risky_operation();
} catch (const std::exception& e) {
    log_error(e);
    cleanup();
    throw;  // Re-throw after cleanup
}

// Bad: Swallowing exceptions
try {
    risky_operation();
} catch (...) {
    // Exception silently ignored!
}

Objective-C Exceptions¶

@try {
    [object riskyMethod];
} @catch (NSException* e) {
    NSLog(@"Exception: %@", e);
    @throw;  // Re-throw
}

Resolution¶

Ensure exception handling is enabled:

# Enable exceptions (usually default)
clang++ -fexceptions program.cpp

# Do NOT disable with -fno-exceptions unless intentional

CMake Configuration¶

# Ensure exceptions are enabled
if(CMAKE_CXX_COMPILER_ID MATCHES "Clang")
    target_compile_options(myapp PRIVATE -fexceptions)
endif()