cve.bz

CWE-111: Direct Use of Unsafe JNI

Filter

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.

What the weakness is: CWE-111 at MITRE. All weaknesses

Ask an AI about CWE-111

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CWE-111: Direct Use of Unsafe JNI and how to prevent and detect it in code. Use https://cwe.mitre.org/data/definitions/111.html and https://cve.bz/cve/cwe/111?via=ask-ai-copy for recent CVEs with this weakness. Cite the sources.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this weakness's id and public links.

  1. 9.8CVE-2018-12549EPSS 2.3%

    In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of an Unsafe call when accelerating it.

  2. 8.1CVE-2016-9160EPSS 1.4%

    A vulnerability in SIEMENS SIMATIC WinCC (All versions < SIMATIC WinCC V7.2) and SIEMENS SIMATIC PCS 7 (All versions < SIMATIC PCS 7 V8.0 SP1) could allow a remote attacker to crash an ActiveX component or leak parts of the application mem…