Skip to content
OpenAdvisories

Weakness (CWE)

CWE-111: Direct Use of Unsafe JNI

Variant Draft

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.

How to prevent it (3 mitigations)
  1. Implementation

    Implement error handling around the JNI call.

  2. Implementation

    Do not use JNI calls if the native library can't be trusted.

  3. Implementation

    Be reluctant to use JNI calls. A Java API equivalent may exist.

Source: MITRE CWE-111

2 results · Feed

  • Unscored —

    In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of a…

  • Unscored —

    A vulnerability in SIEMENS SIMATIC WinCC (All versions < SIMATIC WinCC V7.2) and SIEMENS SIMATIC PCS 7 (All versions < …