VariantDraft

CWE-111Direct Use of Unsafe JNI

Category: other

Description

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. Many safety features that programmers may take for granted do not apply for native code, so you must carefully review all such code for potential problems. The languages used to implement native code may be more susceptible to buffer overflows and other attacks. Native code is unprotected by the security features enforced by the runtime environment, such as strong typing and array bounds checking.

Common consequences· 1

  • Access Control — Bypass Protection Mechanism

Potential mitigations· 3

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

References

  1. https://cwe.mitre.org/data/definitions/111.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Process Control
CWE
Untrusted Pointer Dereference
CWE
Stack-based Buffer Overflow
CWE
Use of NullPointerException Catch to Detect NULL Pointer Dereference
CWE
Uncaught Exception
CAPEC
Escaping a Sandbox by Calling Code in Another Language
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.