1789
Automated static analysis is useful for detecting commonly-used idioms for authorization. A tool
may be able to analyze related configuration files, such as .htaccess in Apache web servers, or
detect the usage of commonly-used authorization libraries. Generally, automated static analysis
tools have difficulty detecting custom authorization schemes. Even if they can be customized to
recognize these schemes, they might not be able to tell whether the scheme correctly performs
the authorization in a way that cannot be bypassed or subverted by an attacker.
Effectiveness = Limited
Automated Dynamic Analysis
Automated dynamic analysis may not be able to find interfaces that are protected by
authorization checks, even if those checks contain weaknesses.
Manual Analysis
This weakness can be detected using tools and techniques that require manual (human)
analysis, such as penetration testing, threat modeling, and interactive tools that allow the
tester to record and modify an active session. Specifically, manual static analysis is useful for
evaluating the correctness of custom authorization mechanisms.
Effectiveness = Moderate
These may be more effective than strictly automated techniques. This is especially the case with
weaknesses that are related to design and business rules. However, manual efforts might not
achieve desired code coverage within limited time constraints.
Manual Static Analysis - Binary or Bytecode
According to SOAR, the following detection techniques may be useful: Cost effective for partial
coverage: Binary / Bytecode disassembler - then use manual analysis for vulnerabilities &
anomalies
Effectiveness = SOAR Partial
Dynamic Analysis with Automated Results Interpretation
According to SOAR, the following detection techniques may be useful: Cost effective for partial
coverage: Web Application Scanner Web Services Scanner Database Scanners
Effectiveness = SOAR Partial
Dynamic Analysis with Manual Results Interpretation
According to SOAR, the following detection techniques may be useful: Cost effective for partial
coverage: Host Application Interface Scanner Fuzz Tester Framework-based Fuzzer Forced
Path Execution Monitored Virtual Environment - run potentially malicious code in sandbox /
wrapper / virtual machine, see if it does anything suspicious
Effectiveness = SOAR Partial
Manual Static Analysis - Source Code
According to SOAR, the following detection techniques may be useful: Cost effective for partial
coverage: Focused Manual Spotcheck - Focused manual analysis of source Manual Source
Code Review (not inspections)
Effectiveness = SOAR Partial
Automated Static Analysis - Source Code
According to SOAR, the following detection techniques may be useful: Cost effective for partial
coverage: Context-configured Source Code Weakness Analyzer
Effectiveness = SOAR Partial
Architecture or Design Review
CWE Version 4.14
CWE-863: Incorrect Authorization
CWE-863: Incorrect Authorization