CWE-111 Direct Use of Unsafe JNI

When a Java application uses the Java Native Interface (JNI) to call code written in another programming language, it can expose the application to weaknesses in that code, even if those weaknesses cannot occur in Java.

• Access Control: Bypass Protection Mechanism

• [Implementation] Implement error handling around the JNI call. • [Implementation] Do not use JNI calls if the native library can't be trusted. • [Implementation] Be reluctant to use JNI calls. A Java API equivalent may exist.

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)