SOFTWARE VULNERABILITY ANALYSIS
Software vulnerability in an automotive system is analyzed by receiving one or more application files of a software application developed for the automotive system; analyzing: the one or more application files based on an automotive system specification, data from one or more security databases, an expert preference, and information about modules and functions of the software application; identifying one or more vulnerabilities in the one or more application files based on the analysis; and updating the one or more databases with the one or more vulnerabilities, wherein the updated one or more databases are used to detect the one or more vulnerabilities in the software application running on the automotive system in real-time, wherein one or more patches are provided to secure the automotive system.
1 . A method of analyzing software vulnerability in an automotive system, the method comprising:
receiving one or more application files of a software application developed for the automotive system:
analyzing the one or more application files based on an automotive system specification, database parameters from one or more databases, an expert preference, and information about modules and functions of the software application;
identifying one or more vulnerabilities in the one or more application files based on the analysis; and
updating the one or more databases with the one or more vulnerabilities, wherein the updated one or more databases are used to detect the threats to the automotive system in real-time, wherein one or more patches are provided to secure the automotive system.
2 . The method of claim 1 , wherein the one or more application files comprises a source file and/or a binary file.
3 . The method of claim 1 , wherein the analyzing comprises static analysis and dynamic analysis, wherein, during the static analysis, the binary file and/or the source code file are checked for compliance with coding standards, and, during dynamic analysis, the binary file and/or the source code file are executed and checked for vulnerabilities during execution.
4 . The method of claim 1 , wherein one or more databases comprises a Common Vulnerabilities and Exposure (CVE) database and a Security Operation Center (SOC) database.
5 . The method of claim 4 , wherein the CVE database comprises information related to a plurality of vulnerabilities, and the SOC database comprises security information related to the automotive system.
6 . The method of claim 1 , wherein the automotive system specification comprises version name, software-update information, hardware information, and network information.
7 . The method of claim 1 , wherein the identifying comprises:
comparing a result of analysis of the one or more application files with the plurality of vulnerabilities in the one or more databases; and
detecting the one or more vulnerabilities based on the comparison.
8 . A system for analyzing software vulnerability in an automotive system, the system comprising:
a memory configured to:
receive one or more application files of a software application developed for the automotive system;
analyze the one or more application files based on an automotive system specification, database parameters from one or more databases, an expert preference, and information about modules and functions of the software application;
identify one or more vulnerabilities in the one or more application files based on the analysis;
update the one or more databases with the one or more vulnerabilities, wherein the updated one or more databases are used to detect threats to the automotive system in real-time, wherein one or more patches are provided to secure the automotive system.
9 . The system of claim 8 , wherein the one or more application files comprises a source file and/or a binary file.
10 . The system of claim 8 , wherein the one or more processors analyze the one or more application files using static analysis and dynamic analysis, wherein, during the static analysis, the binary file and/or the source code file are checked for compliance with coding standards, and, during dynamic analysis, the binary file and/or the source code file are executed and checked for vulnerabilities during execution.
11 . The system of claim 8 , wherein one or more databases comprises a Common Vulnerabilities and Exposure (CVE) database and a Security Operation Center (SOC) database.
12 . The system of claim 11 , wherein the CVE database comprises a plurality of vulnerabilities, and the SOC database comprises security information related to the automotive system.
13 . The system of claim 8 , wherein the automotive system specification comprises version name, software update information, hardware information, and network information.
14 . The system of claim 8 , wherein the one or more processors are configured to identify by:
comparing a result of analysis of the one or more application files with the plurality of vulnerabilities in the one or more databases; and
detecting the one or more vulnerabilities based on the comparison.