Automated security analysis of software libraries
A method for identifying security vulnerabilities in a third party software component includes generating a test application for the third party software component. The test application is generated such that every externally accessible data path in the third party component is called. The test application and the third party software component are analyzed using a static application security testing (SAST) code analyzer. One or more test results are obtained from the SAST code analyzer. The one or more test results are used to identify security vulnerabilities in the third party component.
1 . A method for enhanced security analysis of software components, the method comprising:
generating a non-executable test application that invokes methods within a third-party software component;
analyzing the third-party software component in conjunction with the non-executable test application using a Static Application Security Testing (SAST) code analyzer;
sequentially calling all accessible methods within the third-party software component according to an ordered sequence of method calls;
re-invoking the ordered sequence of method calls a second time to ensure that whereupon a first method modifies an internal state of an object, and a second method is subsequently invoked after the first method, any potential vulnerability arising due to the internal state of the object is identified; and
analyzing the potential vulnerability identified through the ordered sequence of method calls to ensure that all possible code paths within the third-party software component are evaluated.
2 . The method of claim 1 , further comprising integrating a taint checking process, wherein tainted data is injected into the third-party software component during the ordered sequence of method calls, and a presence of tainted data in an output is analyzed to identify potential security vulnerabilities.
3 . The method of claim 2 , further comprising analyzing results of each ordered sequence of method calls using the SAST code analyzer to determine whether the tainted data is generated or propagated by the third-party software component.
4 . The method of claim 1 , further including generating dynamic test data that is passed into the ordered sequence of method calls to simulate real-world data interactions that may arise during typical use.
5 . The method of claim 1 , wherein at least one method call in the ordered sequence of method calls is non-deterministic, to simulate varying execution paths and identify vulnerabilities that may not be apparent under deterministic conditions.
6 . The method of claim 1 , wherein the ordered sequence of method calls includes, in order, all accessible static methods, all accessible constructors, and all singleton style constructors.
7 . The method of claim 1 , wherein the analyzing includes identifying and segregating potential false positive vulnerabilities to refine an accuracy of the enhanced security analysis.
8 . The method of claim 1 , further comprising executing at least one method call in the ordered sequence of method calls more than once with different input parameters each time, to assess how varied inputs affect a behavior of the third-party software component.
9 . The method of claim 1 , wherein the ordered sequence of method calls includes all accessible getter and setter methods, to evaluate an integrity of data encapsulation and access control within the third-party software component.
10 . The method of claim 1 , further comprising compiling the non-executable test application with the third-party software component, and executing a compiled code to assess an integration and interaction between the non-executable test application and the third-party software component.
11 . A computer system for enhancing security analysis of software components, comprising:
one or more processors; and
non-transitory computer readable storage media encoding instructions which, when executed by the one or more processors, cause the computer system to:
generate a non-executable test application that invokes methods within a third-party software component;
analyze the third-party software component in conjunction with the non-executable test application using a Static Application Security Testing (SAST) code analyzer;
sequentially call all accessible methods within the third-party software component according to an ordered sequence of method calls;
re-invoke the ordered sequence of method calls a second time to ensure that whereupon a first method modifies an internal state of an object, and a second method is subsequently invoked after the first method, any potential vulnerability arising due to the internal state of the object is identified; and
analyze the potential vulnerability identified through the ordered sequence of method calls to ensure that all possible code paths within the third-party software component are evaluated.
12 . The computer system of claim 11 , wherein the non-transitory computer readable storage media encoding instructions further cause the computer system to integrate a taint checking process, wherein tainted data is injected into the third-party software component during the ordered sequence of method calls, and a presence of tainted data in an output is analyzed to identify potential security vulnerabilities.
13 . The computer system of claim 12 , wherein the non-transitory computer readable storage media encoding instructions further cause the computer system to analyze results of each ordered sequence of method calls using the SAST code analyzer to determine whether the tainted data is generated or propagated by the third-party software component.
14 . The computer system of claim 11 , wherein the non-transitory computer readable storage media encoding instructions further cause the computer system to generate dynamic test data that is passed into the ordered sequence of method calls to simulate real-world data interactions that may arise during typical use.
15 . The computer system of claim 11 , wherein at least one method call in the ordered sequence of method calls is non-deterministic, to simulate varying execution paths and identify vulnerabilities that may not be apparent under deterministic conditions.
16 . The computer system of claim 11 , wherein the ordered sequence of method calls includes, in order, all accessible static methods, all accessible constructors, and all singleton style constructors.
17 . The computer system of claim 11 , wherein the analyze includes identifying and segregating potential false positive vulnerabilities to refine an accuracy of the security analysis.
18 . The computer system of claim 11 , wherein the non-transitory computer readable storage media encoding instructions further cause the computer system to execute at least one method call in the ordered sequence of method calls more than once with different input parameters each time, to assess how varied inputs affect a behavior of the third-party software component.
19 . The computer system of claim 11 , wherein the ordered sequence of method calls includes all accessible getter and setter methods, to evaluate an integrity of data encapsulation and access control within the third-party software component.
20 . The computer system of claim 11 , wherein the non-transitory computer readable storage media encoding instructions further cause the computer system to compile the non-executable test application with the third-party software component, and execute a compiled code to assess an integration and interaction between the non-executable test application and the third-party software component.