A system and method for detecting security vulnerabilities of open source components

By designing an open source component security vulnerability detection system, using the collaborative work of the vulnerability detection server and client, combining the vulnerability analysis engine and security vulnerability database, the problem of insufficient vulnerability detection in the existing technology is solved, and the efficiency, accuracy and efficiency of open source components is achieved. Secure vulnerability detection reduces security risks.

CN118862098BActive Publication Date: 2024-11-26SUZHOU PRISM COLORFUL INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411321954.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-23
Publication Date
2024-11-26
Estimated Expiration
2044-09-23

AI Technical Summary

Technical Problem

The existing open source component security vulnerability detection technology cannot achieve real-time, comprehensive and in-depth security detection, and there are shortcomings in vulnerability verification and authorization management, resulting in security vulnerabilities that may be missed or falsely positive, increasing the security during the use of open source components. risk.

Method used

An open source component security vulnerability detection system was designed, including a vulnerability detection server and client. It can perform security detection through the open source component vulnerability detection module, and use the vulnerability analysis engine and security vulnerability database to identify and verify vulnerability characteristic values, supporting the developer side. Multi-point connection with the auditor side, generating detection timestamps to ensure traceability of detection results.

Benefits of technology

It realizes rapid identification and response to open source component security vulnerabilities, improves detection accuracy and efficiency, enhances the flexibility and reliability of the detection process, ensures data security and privacy, and supports the vulnerability characteristic value In-depth analysis and verification.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118862098B_ABST
    Figure CN118862098B_ABST
Patent Text Reader

Abstract

The present invention provides a system and method for detecting security vulnerabilities of open source components. The system includes a vulnerability detection server and a client. The system receives detection requests through detection nodes, calculates and stores vulnerability feature values, records timestamps, and distributes results to clients. The client is divided into a developer side and an audit side, which are responsible for initiating detection requests and verifying vulnerabilities, respectively. The audit side can obtain the detection results of the authorized request and perform comparison and verification. The present invention can effectively improve the security of open source components and the efficiency of vulnerability management.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer security technology, and more specifically, to an open source component security vulnerability detection system and method. Background Art

[0002] Existing open source component security vulnerability detection technologies usually rely on manual review or simple automated tools, which often have problems such as low detection efficiency, insufficient accuracy, and delayed updates. The technical principles are mostly based on matching known vulnerability databases and some basic code analysis techniques. However, with the surge in the number of open source components and the diversification of vulnerability types, these methods have been unable to meet the growing security needs.

[0003] In the process of implementing the embodiments of the present invention, the inventors found that there are at least the following problems or defects in the prior art: the existing detection system is unable to achieve real-time, comprehensive and in-depth security detection of open source components, and there are also deficiencies in vulnerability verification and authorization management, which may cause security vulnerabilities to be missed or misreported, thereby increasing the security risks in the use of open source components. Summary of the invention

[0004] The present invention provides a system and method for detecting security vulnerabilities of open source components.

[0005] In a first aspect of the present invention, a system for detecting security vulnerabilities of open source components is provided, comprising:

[0006] Vulnerability detection server and client;

[0007] The vulnerability detection server is used to process security vulnerability detection requests of open source components and store and manage detection results;

[0008] The vulnerability detection server includes an open source component vulnerability detection module as a detection node, carrying a security detection service, and is used to manage the security vulnerability data of the open source component and the authority to access the security vulnerability information of the open source component;

[0009] Receive security vulnerability detection requests from clients and send detection result data to clients point-to-point;

[0010] The client establishes a connection with the vulnerability detection server to initiate a security vulnerability detection request to the vulnerability detection server, obtains detection result data from the open source component vulnerability detection module point-to-point, or initiates a security vulnerability verification request to the vulnerability detection server to determine the existence of a security vulnerability;

[0011] The client is divided into a developer end and an audit end; the developer end is connected to the vulnerability detection server; the audit end is connected to the developer end and the vulnerability detection server respectively;

[0012] When detecting security vulnerabilities in open source components, the developer side initiates a security vulnerability detection request, obtains the address of the open source component vulnerability detection module, and submits detection request information to the open source component vulnerability detection module; the open source component vulnerability detection module verifies the request information, and if the verification is successful, calculates the vulnerability feature value of the open source component, stores the result after security marking the vulnerability feature value, and records the detection timestamp; after the detection is successful, the developer side obtains the detection result data issued point-to-point by the open source component vulnerability detection module;

[0013] When verifying security vulnerabilities, the audit end obtains authorization to verify the security vulnerabilities of open source components from the developer end; after obtaining authorization, the audit end requests detection result data from the open source component vulnerability detection module, and receives the detection result data sent point-to-point after authorization verification by the open source component vulnerability detection module; sends a request to verify the security vulnerability of the open source component to the vulnerability detection server, and obtains the vulnerability feature value of the security vulnerability of the open source component after authorization verification; verifies and compares the detection result data according to the vulnerability feature value to verify the existence of the security vulnerability of the open source component;

[0014] In some embodiments, verifying and comparing the detection result data according to the vulnerability feature value to verify the existence of the security vulnerability of the open source component includes the following steps:

[0015] The audit end obtains verification authorization from the developer end, and receives the open source component information and the timestamp of the component security vulnerability detection provided by the developer end;

[0016] The audit end uses the obtained authorization to request detection result data from the open source component vulnerability detection module;

[0017] The open source component vulnerability detection module performs authorization verification on the audit end's request. If the verification passes, it provides the corresponding detection result data;

[0018] The audit end receives the detection result data and queries the relevant vulnerability feature values ​​from the security vulnerability database;

[0019] The audit end uses the vulnerability analysis engine to analyze the acquired vulnerability feature values ​​to determine their consistency with the detection result data;

[0020] The audit end verifies and compares the detection result data based on the analysis results of the vulnerability analysis engine to confirm whether there are security vulnerabilities in the open source components;

[0021] If the verification results indicate a security vulnerability, the audit side will feed back the information to the developer side and record the verification process and results for further security management and vulnerability repair.

[0022] When the audit end obtains authorization to verify the security vulnerability of the open source component from the developer end, the audit end sends the request authorization information including the user information of the audit end to the developer end; the developer end verifies the authorization information; after the verification is passed, the authorization record of the developer end on the vulnerability detection server is updated and the user information of the audit end is written; the audit end obtains the information of the open source component to be verified from the developer end and the detection timestamp on the vulnerability detection server when the security vulnerability of the component is detected;

[0023] When the open source component vulnerability detection module performs authorization verification, the open source component vulnerability detection module queries whether the authorization record of the verified open source component on the server includes the user information of the audit end; if so, the detection result data of the open source component is returned.

[0024] Furthermore, it also includes a security vulnerability database, which is connected to the vulnerability detection server and is used to store and manage all detected security vulnerability data and provide query services for vulnerability feature values.

[0025] Furthermore, it also includes a vulnerability analysis engine, which is connected to the vulnerability detection server to provide vulnerability analysis services, provide identification of vulnerability feature values ​​for open source components, and respond to security vulnerability verification requests for vulnerability feature value validity verification.

[0026] Furthermore, the vulnerability feature value is non-plaintext data calculated according to a vulnerability analysis algorithm.

[0027] Furthermore, the detection timestamp is a time mark generated according to the rules of the vulnerability detection server when the open source component vulnerability detection module submits the detection result for storage, and is used to point to the security vulnerability detection in the detection record.

[0028] Further, verifying and comparing the detection result data according to the vulnerability feature value, and verifying the existence of the security vulnerability of the open source component includes the following steps:

[0029] The audit end obtains verification authorization from the developer end, and receives the open source component information and the timestamp of the component security vulnerability detection provided by the developer end;

[0030] The audit end uses the obtained authorization to request detection result data from the open source component vulnerability detection module;

[0031] The open source component vulnerability detection module performs authorization verification on the audit end's request. If the verification passes, it provides the corresponding detection result data;

[0032] The audit end receives the detection result data and queries the relevant vulnerability feature values ​​from the security vulnerability database;

[0033] The audit end uses the vulnerability analysis engine to analyze the acquired vulnerability feature values ​​to determine their consistency with the detection result data;

[0034] The audit end verifies and compares the detection result data based on the analysis results of the vulnerability analysis engine to confirm whether there are security vulnerabilities in the open source components;

[0035] If the verification results indicate a security vulnerability, the audit side will feed back the information to the developer side and record the verification process and results for further security management and vulnerability repair.

[0036] In a second aspect of the present invention, a detection method of an open source component security vulnerability detection system is provided, comprising:

[0037] The developer end is connected to the vulnerability detection server, initiates an open source component security vulnerability detection request to the vulnerability detection server, and obtains the detection result from the open source component vulnerability detection module point-to-point;

[0038] The audit end is connected to the developer end and the vulnerability detection server respectively, obtains verification authorization from the developer end, initiates security vulnerability verification to the vulnerability detection server, and determines the accuracy of the detection result provided by the developer end;

[0039] The vulnerability detection server includes an open source component vulnerability detection module as a detection node, carries security detection services, and is used to manage security vulnerability data of open source components and permissions to access security vulnerability information; receives security vulnerability detection or verification requests, and distributes detection result data point-to-point.

[0040] Further, initiating an open source component security vulnerability detection request to the vulnerability detection server includes: the developer end initiating the security vulnerability detection request submits detection request information to the open source component vulnerability detection module according to the acquired open source component vulnerability detection module address;

[0041] The open source component vulnerability detection module verifies the request information, and if the verification is successful, calculates the vulnerability feature value of the open source component, stores the result after security marking the vulnerability feature value, and records the detection timestamp;

[0042] After the detection is successful, the developer side obtains the detection result data issued point-to-point by the open source component vulnerability detection module.

[0043] Further, initiating security vulnerability verification to the vulnerability detection server includes: obtaining authorization for verifying security vulnerabilities of open source components from the developer side;

[0044] After obtaining authorization, request the detection result data from the open source component vulnerability detection module; and receive the detection result data sent point-to-point after authorization verification by the open source component vulnerability detection module;

[0045] Sending a request to verify the security vulnerability of the open source component to the vulnerability detection server, and obtaining the vulnerability feature value of the security vulnerability of the open source component after authorization verification;

[0046] The detection result data is verified and compared according to the vulnerability feature value to verify the existence of the security vulnerability of the open source component.

[0047] According to the above-mentioned embodiments of the present invention, at least the following beneficial effects are achieved: the open source component security vulnerability detection system of the present invention can provide a centralized platform for efficiently detecting and managing security vulnerabilities in open source components. Through the collaborative work of the vulnerability detection server and the client, the system can quickly identify and respond to security vulnerabilities, thereby significantly improving the accuracy and efficiency of detection. In addition, the system supports multi-point connections between the developer side and the audit side, which can ensure the flexibility and reliability of the detection and verification process. The system also includes a security vulnerability database and a vulnerability analysis engine, which can further enhance the ability to identify and verify vulnerability feature values. By using non-plaintext data to calculate vulnerability feature values, the present invention can improve the security and privacy of data. At the same time, the detection timestamp generated by the system can provide an accurate time record for each detection, which helps to track and audit the detection process, and ensure the traceability of the detection results and clear responsibilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The above and other objects, features and advantages of the exemplary embodiments of the present invention will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present invention are shown in an exemplary and non-limiting manner, in which:

[0049] Figure 1 A schematic diagram of the structure of an open source component security vulnerability detection system provided by an embodiment of the present invention;

[0050] Figure 2 A schematic diagram of a flow chart of a detection method of an open source component security vulnerability detection system provided by an embodiment of the present invention;

[0051] Figure 3 The schematic diagram schematically shows the structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0052] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present invention more thorough and complete, and to fully convey the scope of the present invention to those skilled in the art.

[0053] Those skilled in the art know that the embodiments of the present invention can be implemented as a system, device, apparatus, method or computer program product. Therefore, the present invention can be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0054] It should be noted that any number of elements in the drawings is for illustration rather than limitation, and any naming is only for distinction and does not have any limiting meaning.

[0055] Reference below Figure 1 , Figure 1 This is a schematic diagram of the structure of an open source component security vulnerability detection system provided by an embodiment of the present invention. Figure 1 As shown, an open source component security vulnerability detection system 100 includes:

[0056] Vulnerability detection server 101 and client 102;

[0057] The vulnerability detection server is used to process security vulnerability detection requests of open source components and store and manage detection results;

[0058] The vulnerability detection server includes an open source component vulnerability detection module as a detection node, carrying a security detection service, and is used to manage the security vulnerability data of the open source component and the authority to access the security vulnerability information of the open source component;

[0059] Receive security vulnerability detection requests from clients and send detection result data to clients point-to-point;

[0060] The client establishes a connection with the vulnerability detection server to initiate a security vulnerability detection request to the vulnerability detection server, obtains detection result data from the open source component vulnerability detection module point-to-point, or initiates a security vulnerability verification request to the vulnerability detection server to determine the existence of a security vulnerability;

[0061] The client is divided into a developer end and an audit end; the developer end is connected to the vulnerability detection server; the audit end is connected to the developer end and the vulnerability detection server respectively;

[0062] When detecting security vulnerabilities in open source components, the developer side initiates a security vulnerability detection request, obtains the address of the open source component vulnerability detection module, and submits detection request information to the open source component vulnerability detection module; the open source component vulnerability detection module verifies the request information, and if the verification is successful, calculates the vulnerability feature value of the open source component, stores the result after security marking the vulnerability feature value, and records the detection timestamp; after the detection is successful, the developer side obtains the detection result data issued point-to-point by the open source component vulnerability detection module;

[0063] When verifying security vulnerabilities, the audit end obtains authorization to verify the security vulnerabilities of open source components from the developer end; after obtaining authorization, the audit end requests detection result data from the open source component vulnerability detection module, and receives the detection result data sent point-to-point after authorization verification by the open source component vulnerability detection module; sends a request to verify the security vulnerability of the open source component to the vulnerability detection server, and obtains the vulnerability feature value of the security vulnerability of the open source component after authorization verification; verifies and compares the detection result data according to the vulnerability feature value to verify the existence of the security vulnerability of the open source component;

[0064] When the audit end obtains authorization to verify the security vulnerability of the open source component from the developer end, the audit end sends the request authorization information including the user information of the audit end to the developer end; the developer end verifies the authorization information; after the verification is passed, the authorization record of the developer end on the vulnerability detection server is updated and the user information of the audit end is written; the audit end obtains the information of the open source component to be verified from the developer end and the detection timestamp on the vulnerability detection server when the security vulnerability of the component is detected;

[0065] When the open source component vulnerability detection module performs authorization verification, the open source component vulnerability detection module queries whether the authorization record of the verified open source component on the server includes the user information of the audit end; if so, the detection result data of the open source component is returned.

[0066] It should be noted that the vulnerability detection server carries the security detection service, which is responsible for receiving security vulnerability detection requests from the client and providing detection results. The developer side is part of the client, which initiates detection requests to the vulnerability detection server and receives detection results. The audit side is used to verify the accuracy of the detection results provided by the developer side. It needs to obtain authorization from the developer side and interact with the vulnerability detection server to obtain the detection result data. In this system, the detection result data can include information such as vulnerability feature values ​​and detection timestamps, and authorization involves controlling the access rights of the audit side.

[0067] Preferably, the vulnerability detection server can be further subdivided into multiple detection nodes, each of which is responsible for processing a specific type of security vulnerability detection task. For example, one node can be set up to specifically handle the detection of SQL injection vulnerabilities, and another node can handle the detection of cross-site scripting (XSS) vulnerabilities. Each detection node can use a specific vulnerability analysis algorithm to calculate the vulnerability feature value, and the formula can be expressed as:

[0068]

[0069] in, Represents the vulnerability feature value, represents the analysis algorithm, Represents the component code. In addition, the detection timestamp can be generated by the server's internal clock to ensure that the time of each detection can be accurately recorded. For authorization verification, a role-based access control (RBAC) model can be adopted to ensure that only users with appropriate authorization can access the detection results.

[0070] Among them, when applied, for the detection of SQL injection vulnerabilities, the analysis algorithm fSQL can be defined as:

[0071]

[0072] Where C is the component code and FVSQL is the characteristic value of the SQL injection vulnerability. The algorithm analyzes how input parameters are handled, checking for proper input sanitization and parameterized query implementation to identify potential SQL injection risks. The goal is to identify places in the code that could allow an attacker to inject malicious SQL code through user input. It checks if the database query uses dynamic concatenation, specifically checking if user input is inserted directly into the SQL statement. The algorithm looks for the use of parameterized queries, which is a key security measure to prevent SQL injection.

[0073] For the detection of cross-site scripting (XSS) vulnerabilities, the analysis algorithm fXSS can be defined as:

[0074]

[0075] Where C is the component code, O is the user input data, and FVXSS is the characteristic value of the XSS vulnerability. The algorithm can check the implementation of output encoding to ensure that all user input is properly escaped before being output to the page. The algorithm is used to identify points in the code that may allow attackers to inject malicious scripts through user input. It checks whether the user input is properly HTML escaped when it is output to the page. The algorithm analyzes the output encoding strategy of the web application to ensure that all user input is properly processed before being displayed to other users to prevent the execution of malicious scripts.

[0076] For the detection of command injection vulnerabilities, the analysis algorithm fCMD can be defined as:

[0077]

[0078] Among them, C is the component code, which is the part of the code in the application that may have vulnerabilities. I represents the data entered by the user, which may be maliciously constructed to try to trigger the command injection vulnerability.

[0079] FVCMD stands for the characteristic value of command injection vulnerability, which is a value calculated by the algorithm to indicate whether there is a potential command injection vulnerability after the combination of code and input data. The purpose of the algorithm is to analyze the interaction between component code C and user input I to determine whether there is a situation where user input is directly used for system commands. If the algorithm finds that there is such an implementation in the code, it will calculate a characteristic value FVCMD, which can be used to mark and identify potential command injection vulnerabilities. In order to ensure that user input is properly escaped before being output to the page, the algorithm checks the implementation of output encoding. Escaping is a security measure that ensures that special characters entered by the user (such as quotes, semicolons, etc.) are not interpreted as part of the command, but are processed as normal text. If the algorithm finds that the output encoding is not implemented correctly, it will mark this risk and prompt the developer to fix this security issue.

[0080] For the detection of insecure direct object reference (IDOR) vulnerabilities, the analysis algorithm fIDOR can be defined as:

[0081]

[0082] Where C is the component code, R is the requested resource identifier, and FVIDOR is the characteristic value of the IDOR vulnerability. The algorithm may analyze the resource access control logic to determine if there is a risk of unauthorized access to sensitive resources. The purpose of the algorithm is to detect direct object references in the application that may allow unauthorized users to access sensitive data or resources. It analyzes the access control logic of the application to ensure that each user can only access the resources they are authorized to. The algorithm checks whether resource access requests are accompanied by appropriate authentication and authorization checks to prevent IDOR vulnerabilities.

[0083] In some embodiments, a security vulnerability database is also included, which is connected to the vulnerability detection server and is used to store and manage all detected security vulnerability data and provide query services for vulnerability feature values.

[0084] It should be noted that the security vulnerability database is set up to ensure that all detected security vulnerability data can be effectively stored and managed, while providing query services for vulnerability feature values, which is crucial for quickly locating and responding to security vulnerabilities.

[0085] Specifically, the security vulnerability database can be a structured data storage system that contains multiple fields, such as vulnerability ID, vulnerability type, impact range, vulnerability description, repair suggestions, etc. These fields together constitute a comprehensive vulnerability information archive, allowing the database to record the relevant information of each vulnerability in detail. In terms of parameter settings, data can be organized according to factors such as the severity of the vulnerability, the time of discovery, and the affected component version, so as to facilitate efficient query and analysis.

[0086] Preferably, the security vulnerability database can adopt a distributed storage architecture to improve data access speed and system scalability. In addition, the database can integrate advanced query algorithms, such as full-text search engines, to support complex query requirements. In order to further enhance data security, encrypted storage and access control mechanisms can be implemented to ensure that only authorized users can access sensitive vulnerability data. At the same time, the database can also be backed up regularly to prevent data loss or damage.

[0087] In some embodiments, a vulnerability analysis engine is also included, which is connected to the vulnerability detection server to provide vulnerability analysis services, provide identification of vulnerability feature values ​​for open source components, and respond to security vulnerability verification requests for validation of vulnerability feature values.

[0088] It should be noted that the connection between the vulnerability analysis engine and the vulnerability detection server is to provide a deeper vulnerability analysis service. The engine can not only identify vulnerability feature values, but also respond to verification requests from the audit end or the developer end for the validity of these feature values. This shows that the system has the ability to conduct in-depth analysis and real-time response to security vulnerabilities, thereby improving the accuracy of detection and response speed.

[0089] Specifically, a vulnerability analysis engine can be an independent software module or service that identifies and analyzes vulnerability signatures through preset algorithms and rule bases. These algorithms may include techniques such as static code analysis and dynamic behavior analysis, while the rule base contains patterns and behavioral characteristics of known vulnerabilities. Parameter settings may involve the depth and frequency of analysis, as well as the priority of identifying different types of vulnerabilities. Conceptually, a vulnerability analysis engine can include a variety of detection technologies, such as fuzz testing, code auditing, etc., to adapt to different types of open source components and security requirements.

[0090] Preferably, the vulnerability analysis engine can use machine learning technology to continuously optimize its recognition capabilities and improve the accuracy of identifying new vulnerabilities by analyzing historical data. In addition, the engine can set multiple detection levels to adapt to scenarios with different security requirements, such as in-depth comprehensive detection during the development phase and fast real-time detection in the production environment. As an alternative, the engine can also integrate third-party security analysis tools or services to enhance its functionality and coverage.

[0091] In some embodiments, the vulnerability feature value is non-plaintext data calculated according to a vulnerability analysis algorithm.

[0092] It should be noted that the vulnerability feature value is non-plaintext data calculated according to the vulnerability analysis algorithm, which emphasizes that the generation process of the vulnerability feature value is automated and encrypted to ensure the security and privacy of the detection results. This means that when the vulnerability detection service processes and stores data, it does not use the original, readable vulnerability information, but converts it into a format that can only be interpreted by authorized entities.

[0093] Specifically, the vulnerability analysis algorithm can be one or more combined algorithms, such as a machine learning-based pattern recognition algorithm, a static code analysis algorithm, or a dynamic behavior analysis algorithm. These algorithms will analyze the code of the open source component, identify potential security vulnerabilities, and convert them into a unique, encrypted vulnerability feature value. Parameter settings may include the sensitivity of the algorithm, the threshold of the false alarm rate, and the selection of the encryption algorithm. Conceptually, the vulnerability feature value can include an encrypted representation of information such as the vulnerability type, location, severity level, and potential impact.

[0094] Preferably, the process of generating vulnerability signatures can be further refined into several key steps: first, the algorithm scans the code of the open source component to identify potential security issues; second, these issues are converted into a standardized format through the algorithm; then, these standardized data are encrypted using the Advanced Encryption Standard (AES) or other encryption technologies to generate the final vulnerability signature value. As an alternative, blockchain-based technology can be used to ensure the immutability and integrity of the data, further improving the security of the system.

[0095] In some embodiments, the detection timestamp is a time stamp generated according to the rules of the vulnerability detection server when the open source component vulnerability detection module submits the detection result for storage, and is used to point to the security vulnerability detection in the detection record.

[0096] It should be noted that the vulnerability characteristic value is non-plaintext data calculated according to the vulnerability analysis algorithm, which emphasizes the security and confidentiality of the system when processing security vulnerability data. By using non-plaintext data, sensitive information can be prevented from being intercepted or tampered with during transmission, thereby improving the security of the system.

[0097] Specifically, the vulnerability signature is the key data obtained by analyzing the open source components through a specific algorithm. This data can represent the uniqueness of the vulnerability and is used in the subsequent detection and verification process. For example, a hash function can be used to process the relevant information of the vulnerability to generate a fixed-length hash value as the vulnerability signature. Parameter settings may include the selected hash algorithm type (such as SHA-256), the number of iterations, etc. These parameters can be adjusted according to actual security needs and performance requirements.

[0098] Preferably, the process of calculating the vulnerability signature value can be further refined. For example, when generating a hash value, you can choose to use salting technology to increase the complexity of the hash value so that the same input generates different hash values ​​in different sessions, thereby improving security. In addition, multiple rounds of hashing can be used, that is, multiple hash operations are performed on the same input, and each operation uses different parameters or algorithms to enhance the security of the generated vulnerability signature value. The formula can be expressed as:

[0099]

[0100] in, represents a hash function, Represents the data concatenation operation, is a randomly generated salt value, This is information about the vulnerability.

[0101] More specifically, the process of generating the vulnerability signature value may include the following steps:

[0102] 1. Collect relevant information about the vulnerability, such as component name, version number, vulnerability description, etc.

[0103] 2. Choose a secure hashing algorithm, such as SHA-256.

[0104] 3. Generate a random salt value to increase the randomness of the hash value.

[0105] 4. Concatenate the salt value with the vulnerability information and then perform a hash operation.

[0106] 5. Multiple rounds of hashing can be performed as needed, with different parameters or algorithms used in each round.

[0107] The above-mentioned various embodiments of the present invention have the following beneficial effects: the open source component security vulnerability detection system of the present invention enables the vulnerability detection server to efficiently process detection requests from the client through its unique architectural design, and accurately store and manage the detection results. The open source component vulnerability detection module in the system acts as a detection node, which can not only manage security vulnerability data, but also control access rights to these data, thereby ensuring the security of the detection process and the confidentiality of the data. The developer end and the audit end of the client can quickly obtain the detection results through a point-to-point connection with the server. At the same time, the audit end can verify the accuracy of the detection results after obtaining authorization, thereby enhancing the credibility of the entire system.

[0108] In addition, the system also includes a security vulnerability database and a vulnerability analysis engine, which are connected to the vulnerability detection server and can not only store and manage the detected security vulnerability data, but also provide query services for vulnerability feature values, as well as in-depth analysis and identification of vulnerability feature values. This design enables the system to quickly respond to security vulnerability verification requests, improving the efficiency and accuracy of vulnerability detection. The non-plaintext processing of vulnerability feature values ​​and the introduction of detection timestamps can further enhance the security and traceability of detection results, ensuring the transparency and accountability of detection activities.

[0109] like Figure 2 As shown, a detection method 200 of an open source component security vulnerability detection system in some embodiments includes:

[0110] Step 201, the developer end is connected to the vulnerability detection server, initiates an open source component security vulnerability detection request to the vulnerability detection server, and obtains the detection result from the open source component vulnerability detection module point-to-point;

[0111] Step 202: the audit end is connected to the developer end and the vulnerability detection server respectively, obtains verification authorization from the developer end, initiates security vulnerability verification to the vulnerability detection server, and determines the accuracy of the detection result provided by the developer end;

[0112] The vulnerability detection server includes an open source component vulnerability detection module as a detection node, carries security detection services, and is used to manage security vulnerability data of open source components and permissions to access security vulnerability information; receives security vulnerability detection or verification requests, and distributes detection result data point-to-point.

[0113] It is understandable that the steps described in the detection method 200 of the open source component security vulnerability detection system are similar to those described in the reference Figure 1Therefore, the modules, features and beneficial effects described above for the open source component security vulnerability detection system are also applicable to the detection method 200 of the open source component security vulnerability detection system and the operations contained therein, which will not be repeated here.

[0114] In some embodiments, initiating an open source component security vulnerability detection request to a vulnerability detection server includes: a developer end initiating the security vulnerability detection request submitting detection request information to an open source component vulnerability detection module according to an acquired open source component vulnerability detection module address;

[0115] The open source component vulnerability detection module verifies the request information, and if the verification is successful, calculates the vulnerability feature value of the open source component, stores the result after security marking the vulnerability feature value, and records the detection timestamp;

[0116] After the detection is successful, the developer side obtains the detection result data issued point-to-point by the open source component vulnerability detection module.

[0117] It should be noted that when the developer initiates a security vulnerability detection request, it is necessary to provide information including but not limited to the name, version number, and programming language of the open source component. This information will be used to identify and locate specific open source components and match them in the vulnerability detection service. At the same time, the developer needs to set corresponding parameters according to the interface specifications provided by the vulnerability detection service, such as the request timeout and the format of the result return.

[0118] Preferably, when submitting the detection request information, the developer can use encrypted transmission to ensure the security of the request information during network transmission. In addition, when verifying the request information, the open source component vulnerability detection module can verify the identity of the developer in addition to basic format and parameter checks to ensure the legitimacy of the request. When calculating the vulnerability feature value, the service can use a variety of vulnerability analysis algorithms and select the most appropriate algorithm for detection based on the characteristics of the component and the update of the vulnerability database.

[0119] In some embodiments, initiating security vulnerability verification to a vulnerability detection server includes: obtaining authorization to verify security vulnerabilities of open source components from a developer;

[0120] After obtaining authorization, request the detection result data from the open source component vulnerability detection module; and receive the detection result data sent point-to-point after authorization verification by the open source component vulnerability detection module;

[0121] Sending a request to verify the security vulnerability of the open source component to the vulnerability detection server, and obtaining the vulnerability feature value of the security vulnerability of the open source component after authorization verification;

[0122] The detection result data is verified and compared according to the vulnerability feature value to verify the existence of the security vulnerability of the open source component.

[0123] It should be noted that this section will explain in detail the process of initiating security vulnerability verification to the vulnerability detection server. This process involves obtaining authorization between the audit end and the developer end, interacting with the vulnerability detection service, and verifying and comparing the detection results.

[0124] Specifically, the audit side first needs to obtain authorization from the developer side to verify the security vulnerabilities of open source components. This involves the audit side sending request authorization information containing its own user information to the developer side, and the developer side verifies this information. After successful verification, the developer side updates the authorization record on the vulnerability detection server and writes the user information of the audit side. This step ensures that the audit side has the right to access and verify the detection results.

[0125] Preferably, the authorization verification process can be further refined. For example, the developer side can set specific parameters to define the scope and permission level of authorization, such as only allowing the audit side to access the detection results of a specific component. In addition, after obtaining authorization, the audit side can request the detection result data from the vulnerability detection service and receive the data sent point-to-point after the service authorization verification. This step can enhance the security of data transmission through encrypted communication.

[0126] More specifically, after receiving the detection result data, the audit end can further perform verification operations. This includes verifying and comparing the detection results using vulnerability feature values ​​to confirm the existence of security vulnerabilities in open source components. In order to improve the accuracy of verification, the system can use a variety of vulnerability analysis algorithms to calculate and compare vulnerability feature values. In addition, a feedback mechanism can be set up to allow the audit end to report to the developer end or vulnerability detection server when problems are found, so as to correct and update the detection results in a timely manner.

[0127] Reference below Figure 3 , which shows a schematic diagram of the structure of an electronic device 300 suitable for implementing some embodiments of the present invention. The electronic devices in some embodiments of the present invention may include but are not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 3 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0128] like Figure 3As shown, the electronic device 300 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 to a random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic device 300 are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0129] Typically, the following devices may be connected to the I / O interface 305: an input device 306 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 307 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 308 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 309. The communication device 309 may allow the electronic device 300 to communicate with other devices wirelessly or by wire to exchange data. Figure 3 The electronic device 300 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 3 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0130] Furthermore, the storage medium of the embodiment of the present application stores program instructions that can implement all the above methods, wherein the program instructions can be stored in the above storage medium in the form of a software product, including several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or terminal devices such as a computer, a server, a mobile phone, and a tablet.

[0131] The above descriptions are only some preferred embodiments of the present invention and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present invention is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above inventive concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present invention.

Claims

1. An open source component security vulnerability detection system, characterized in that: include: Vulnerability detection server and client; The vulnerability detection server is used to process security vulnerability detection requests of open source components and store and manage detection results; The vulnerability detection server includes an open source component vulnerability detection module as a detection node, carrying a security detection service, and is used to manage the security vulnerability data of the open source component and the authority to access the security vulnerability information of the open source component; Receive security vulnerability detection requests from clients and send detection result data to clients point-to-point; The client establishes a connection with the vulnerability detection server to initiate a security vulnerability detection request to the vulnerability detection server, obtains detection result data from the open source component vulnerability detection module point-to-point, or initiates a security vulnerability verification request to the vulnerability detection server to determine the existence of a security vulnerability; The client is divided into a developer end and an audit end; the developer end is connected to the vulnerability detection server; The audit end is connected to the developer end and the vulnerability detection server respectively; When detecting security vulnerabilities in open source components, the developer initiates a security vulnerability detection request, obtains the address of the open source component vulnerability detection module, and submits detection request information to the open source component vulnerability detection module; the open source component vulnerability detection module verifies the request information. If the verification is successful, the open source component vulnerability detection module calculates the vulnerability feature value of the open source component, stores the result after security marking the vulnerability feature value, and records the detection timestamp; After the detection is successful, the developer side obtains the detection result data issued point-to-point by the open source component vulnerability detection module; During security vulnerability verification, the audit end obtains authorization to verify the security vulnerability of the open source component from the developer end; after obtaining authorization, requests detection result data from the open source component vulnerability detection module, and receives the detection result data sent point-to-point after authorization verification by the open source component vulnerability detection module; sends a request to verify the security vulnerability of the open source component to the vulnerability detection server, and obtains the vulnerability feature value of the security vulnerability of the open source component after authorization verification; Verifying and comparing the detection result data according to the vulnerability feature value to verify the existence of the security vulnerability of the open source component; When the audit end obtains authorization to verify the security vulnerability of the open source component from the developer end, the audit end sends request authorization information including the user information of the audit end itself to the developer end; The developer verifies the authorization information. After verification, the developer updates the authorization record on the vulnerability detection server and writes the user information on the audit side. The audit end obtains the information of the open source component to be verified from the developer end and obtains the detection timestamp of the component security vulnerability detection on the vulnerability detection server; During the authorization verification of the open source component vulnerability detection module, the open source component vulnerability detection module queries whether the authorization record of the verified open source component on the server includes the user information of the audit end; If yes, the detection result data of the open source component is returned.

2. The open source component security vulnerability detection system according to claim 1, characterized in that: It also includes a security vulnerability database, which is connected to the vulnerability detection server and is used to store and manage all detected security vulnerability data and provide query services for vulnerability feature values.

3. The open source component security vulnerability detection system according to claim 2, characterized in that: It also includes a vulnerability analysis engine, which is connected to the vulnerability detection server to provide vulnerability analysis services, provide identification of vulnerability feature values ​​for open source components, and respond to security vulnerability verification requests for validation of vulnerability feature values.

4. The open source component security vulnerability detection system according to claim 1, characterized in that: The vulnerability characteristic value is non-plaintext data calculated according to the vulnerability analysis algorithm.

5. The open source component security vulnerability detection system according to claim 1, characterized in that: The detection timestamp is a time mark generated according to the rules of the vulnerability detection server when the open source component vulnerability detection module submits the detection result for storage, and is used to point to the security vulnerability detection in the detection record.

6. A detection method using the open source component security vulnerability detection system according to any one of claims 1 to 5, characterized in that: The developer end is connected to the vulnerability detection server, initiates an open source component security vulnerability detection request to the vulnerability detection server, and obtains the detection result from the open source component vulnerability detection module point-to-point; The audit end is connected to the developer end and the vulnerability detection server respectively, obtains verification authorization from the developer end, initiates security vulnerability verification to the vulnerability detection server, and determines the accuracy of the detection result provided by the developer end; The vulnerability detection server includes an open source component vulnerability detection module as a detection node, carries security detection services, and is used to manage security vulnerability data of open source components and permissions to access security vulnerability information; receives security vulnerability detection or verification requests, and distributes detection result data point-to-point.

7. The detection method according to claim 6, characterized in that: Initiating an open source component security vulnerability detection request to the vulnerability detection server includes: the developer end initiating the security vulnerability detection request submits detection request information to the open source component vulnerability detection module according to the acquired open source component vulnerability detection module address; The open source component vulnerability detection module verifies the request information, and if the verification is successful, calculates the vulnerability feature value of the open source component, stores the result after security marking the vulnerability feature value, and records the detection timestamp; After the detection is successful, the developer side obtains the detection result data issued point-to-point by the open source component vulnerability detection module.

8. The detection method according to claim 6, characterized in that: Initiating security vulnerability verification to the vulnerability detection server includes: obtaining authorization for verifying the security vulnerability of the open source component from the developer; After obtaining authorization, request the detection result data from the open source component vulnerability detection module; and receive the detection result data sent point-to-point after authorization verification by the open source component vulnerability detection module; Sending a request to verify the security vulnerability of the open source component to the vulnerability detection server, and obtaining the vulnerability feature value of the security vulnerability of the open source component after authorization verification; The detection result data is verified and compared according to the vulnerability feature value to verify the existence of the security vulnerability of the open source component.

9. The detection method according to claim 6, characterized in that: Verifying and comparing the detection result data according to the vulnerability feature value, and verifying the existence of the security vulnerability of the open source component includes the following steps: The audit end obtains verification authorization from the developer end, and receives the open source component information and the timestamp of the component security vulnerability detection provided by the developer end; The audit end uses the obtained authorization to request detection result data from the open source component vulnerability detection module; The open source component vulnerability detection module performs authorization verification on the audit end's request. If the verification passes, it provides the corresponding detection result data; The audit end receives the detection result data and queries the relevant vulnerability feature values ​​from the security vulnerability database; The audit end uses the vulnerability analysis engine to analyze the acquired vulnerability feature values ​​to determine their consistency with the detection result data; The audit end verifies and compares the detection result data based on the analysis results of the vulnerability analysis engine to confirm whether there are security vulnerabilities in the open source components; If the verification results indicate a security vulnerability, the audit side will feed back the information to the developer side and record the verification process and results for further security management and vulnerability repair.