Native methods are defined in Java and written in traditional languages such as C/C++. The added extensibility comes at the cost of flexibility and portability as the code no longer conforms to the policies enforced by Java.
Noncompliant Code Example
Security manager checks are not conducted in case of native method invocations. Additionally, as demonstrated in the noncompliant code example, it is easy to overlook proper input validation before the call. The doOperation
method invokes the nativeOperation
native method but fails on multiple validation angles. Also, the access specifier of the native method is public
which raises risks associated with untrusted callers. (Note that native methods may even increase susceptibility to non-Java specific vulnerabilities, such as buffer overflows)
public final class NativeMethod { // private native method public native void nativeOperation(byte[] data, int offset, int len); // wrapper method that does not perform any security checks or input validation public void doOperation(byte[] data, int offset, int len) { nativeOperation(data, offset, len); } static { System.loadLibrary("NativeMethodLib"); //load native library in static initializer of class } }
Compliant Solution
This compliant solution defines a public wrapper that calls securityManagerCheck()
which in turn performs routine permission checks to determine if the succeeding operations can continue. This is followed by input range checking and creation of a copy of the mutable input array, data. Finally the nativeOperation
method is called with sanitized inputs. Ensure that the validation checks produce outputs that are coherent with the input requirements of the native implementations/libraries.
public final class NativeMethodWrapper { // private native method private native void nativeOperation(byte[] data, int offset, int len); // wrapper method performs SecurityManager and input validation checks public void doOperation(byte[] data, int offset, int len) { // permission needed to invoke native method securityManagerCheck(); if (data == null) { throw new NullPointerException(); } // copy mutable input data = data.clone(); // validate input if ((offset < 0) || (len < 0) || (offset > (data.length - len))) { throw new IllegalArgumentException(); } nativeOperation(data, offset, len); } static { System.loadLibrary("NativeMethodLib"); //load native library in static initializer of class } }
Risk Assessment
TODO
Rule |
Severity |
Likelihood |
Remediation Cost |
Priority |
Level |
---|---|---|---|---|---|
SEC33-J |
?? |
?? |
?? |
P?? |
L?? |
Automated Detection
TODO
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
References
Secure coding in Java http://java.sun.com/security/seccodeguide.html
Java Native Interface: Programmer's Guide and Specification
Java Network Security, 2.2.3 Interfaces and Architectures