Method for securely operating software component

By using weak link scanners in the CI/CD pipeline to identify and deal with weak links in software components, temporarily adapting the deployment configuration, the security vulnerabilities caused by weak links in the software component update process are solved, and zero-day vulnerabilities are achieved Effective handling reduces the risk of cyber attacks.

CN118946884AActive Publication Date: 2024-11-12SIEMENS AG
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202380030081.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-25
Filing Date
2023-03-09
Publication Date
2024-11-12
Estimated Expiration
2043-03-09

AI Technical Summary

Technical Problem

In the process of software component updates, weak links can lead to security vulnerabilities, especially in the Continuous Integration/Continuous Delivery (CI/CD) pipeline, which is difficult to quickly identify and eliminate zero-day vulnerabilities, resulting in an increased risk of cybersecurity attacks.

Method used

By retrieving the deployment information of software components, verifying whether there are weak links in the program components, and deploying them according to the runtime limit information, temporarily adapting the deployment configuration to reduce the risk of vulnerability utilization, and using the weak link scanner to automatically execute in the CI/CD pipeline Scan and process weak links.

Benefits of technology

Effectively identify and temporarily eliminate weak links in software components, reduce the risk of zero-day vulnerability utilization, improve software security, and ensure the safe operation of software components during the update process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118946884A_ABST
    Figure CN118946884A_ABST
Patent Text Reader

Abstract

Method for updating a software component, comprising the steps of: retrieving (A1) deployment information for the software component, the deployment information (11) comprising information about program components of the software component and its runtime configuration; checking (A2) whether at least one program component has a weakness and identifying the program component; determining (A3) a runtime limit for the program component identified with the weak link; inserting (S6) the runtime restriction information into the deployment information (11) for the software component; and executing (A4) the deployment of the software component according to the deployment information (11), wherein the software component is subjected to runtime limitation according to the runtime limitation information when the software component is executed. Evaluating and temporarily adapting runtime configuration information of a deployment configuration for weakness handling in a software component to be updated facilitates handling of usability of zero-day vulnerability utilization.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a method for safely running one or more software components, for example in a computer-controlled industrial automation system. The present invention is particularly applicable within the scope of a continuous integration / continuous delivery (CI / CD) pipeline. Background Art

[0002] In many cases, software components are updated by deploying software containers. When updating, weak links may appear in the changed software components, which must be considered as security vulnerabilities.

[0003] Container images or container instances derived from them on the runtime environment as well as operating systems or application components may contain such vulnerabilities. In many cases, the vulnerabilities are faulty or missing checks of passed parameters in function calls. These vulnerabilities can be exploited by attackers, for example, by passing specially prepared passed parameters to socket functions or function calls in normal program code through exposed interfaces.

[0004] Attack techniques based on this, such as remote code execution, SQL injection or obtaining privileged authorization, can achieve network security attacks, which should be prevented.

[0005] If weak links are identified, they can be published, for example, in publicly accessible databases, such as on the manufacturer's website or an aggregate database. At the same time, the manufacturer of the software component in question usually introduces a elimination process, for example by adapting parameter checks in the program code and providing newer versions of the software components.

[0006] This way of operating is part of the general software development process. However, the manufacturer of the respective software only maintains the software components that it supports. From a date defined by the manufacturer, older versions are no longer maintained. Furthermore, it is often the case that in an open source environment, responsibilities are shared, so that on the one hand, components such as libraries or programs are maintained by the manufacturer of the program. On the other hand, the updated components are then packaged and preconfigured by the distributor and go through a release process. This delays the rapid elimination of critical weaknesses.

[0007] There is a risk that software components containing vulnerabilities are never updated or are not immediately eliminated. As long as the vulnerabilities have not been eliminated, we speak of zero-day vulnerabilities or zero-day exploits.

[0008] There is a desire for a solution that identifies known weaknesses in software components on a system or container instance that have not yet been eliminated by a patch and eliminates their exploitability, at least temporarily, until a fix is ​​provided. Summary of the invention

[0009] Against this background, the object of the present invention is to provide secure operation of the software, in particular when software components are to be updated.

[0010] Accordingly, a method for securely operating a software component is proposed, comprising the following steps:

[0011] retrieving deployment information for a software component, wherein the deployment information includes information about program components of the software component and its runtime configuration;

[0012] Checking whether at least one program component has a vulnerability and identifying the program component;

[0013] Determine runtime restrictions on program components identified as vulnerable;

[0014] inserting the runtime constraint information into deployment information for the software component; and

[0015] The software component is deployed according to the deployment information, wherein runtime restrictions are imposed on the software component according to the runtime restriction information when the software component is executed.

[0016] Evaluating and, in particular, temporarily adapting the runtime configuration information of the deployment configuration for vulnerability handling in the software component to be updated facilitates handling of the usability of zero-day vulnerability exploits, which may be due to a changed runtime configuration for a program component identified as vulnerable.

[0017] Execute or run the corresponding software components in a suitable processing or production environment.

[0018] Weak points include, for example, the possibility of passing unchecked parameters and / or unexpected function calls by software components. For example, adapting the deployment information when identifying weak points can enable temporary privilege revocation for software components, so that the risk of damage is reduced.

[0019] In an embodiment, in this regard, the runtime restrictions include access rights restrictions and / or restrictions on the export of passed parameters or function calls to other software components.

[0020] Preferably, the method is automatically performed within the scope of a build pipeline, which is, for example, part of a CI / CD pipeline. The method is performed in particular in a computer-implemented manner, for example, by a vulnerability scanning process. We also refer to a vulnerability scanner or, hereinafter, also referred to as a scanner.

[0021] In an embodiment, a vulnerability scanner is installed in a CI / CD pipeline, wherein the vulnerability scanner does not only analyze the software component image or the software image itself, but additionally evaluates the deployment information. The used software container image is referenced in the deployment information (e.g., a Kubernetes yaml file or a Docker Compose file), and the used software container image contains binary programs and libraries or software libraries. The deployment information also contains instructions about its runtime configuration, such as specific runtime restrictions. The latter can be analyzed or searched by the vulnerability scanner, whereby one / more software components involved in the vulnerability can be identified.

[0022] In an embodiment, a software component is implemented as an instance of a software container, and the belonging software container image includes package information, binary files, libraries, and configuration data as program components.

[0023] In an embodiment, deploying includes creating an adapted software container image for the software component according to the deployment information supplemented with runtime constraints.

[0024] In an embodiment, the adapted software container image is then functionally verified in a secure processing environment before deployment. For example, a build pipeline causes the generation of an adapted software container image and performs tests on corresponding software components with the aid of a code repository.

[0025] The software components can be deployed in a runtime environment such as Docker. It is also conceivable here to orchestrate the software containers, for example, by means of Kubernetes.

[0026] Preferably, the deployment information references one or more software container images.

[0027] In an embodiment, the runtime constraint information is inserted via a merge request to a build pipeline that causes an update of a software component.

[0028] For example, a vulnerability scanner generates a merge request that is executed by a build pipeline initiated through a code repository.

[0029] In an embodiment, verifying whether at least one program component has a vulnerability comprises searching through the deployment information and / or scanning the software container image, for example in the manner of a vulnerability scanner.

[0030] In an embodiment, the method further comprises:

[0031] Supplementing the deployment information with vulnerability information, which is assigned to the identified software component and / or identifies a program component with a vulnerability, wherein the vulnerability information includes in particular the existence of the vulnerability and / or the elimination of the vulnerability by runtime restrictions, and / or

[0032] Vulnerability information assigned to the identified software components and / or program components identified as having vulnerabilities is stored in a vulnerability database.

[0033] The vulnerability database can be retrieved during a new software update and its contents used to configure the vulnerability scanner.

[0034] In an embodiment, the method further comprises the steps of: searching the deployment information for the software component for vulnerability information assigned to the software component and / or the identified program component; and

[0035] Deployment of the software component is performed based on the vulnerability information.

[0036] In one embodiment, checking whether at least one program component has a weak link further comprises:

[0037] The vulnerability information is stored as configuration data in the vulnerability database for use in the vulnerability scanning process.

[0038] Furthermore, a method for operating a processing system is proposed, which is set up to provide one or more software functions, wherein a plurality of interacting software components are executed in a runtime environment. In this method, one of the software components is updated according to a method as described above or below.

[0039] The corresponding software components can be implemented as instances in a processing environment, in particular as software services or cloud services and / or can also be implemented in hardware technology. When implemented in software technology, the corresponding software functions can be configured as a computer program product, a function, a routine, a part of a program code or an executable object.

[0040] Furthermore, a computer program product is proposed, which comprises instructions which, when the program is executed by a computer, cause the computer to carry out the above method.

[0041] A computer program product, such as a computer program component, can be provided or supplied, for example, as a storage medium, such as a memory card, a USB stick, a CD-ROM, a DVD, or in the form of a file that can be downloaded from a server in a network. This can be done, for example, in a wireless communication network by transmitting a corresponding file with the computer program product or the computer program component.

[0042] The proposed measures during software updates allow not only the used software components themselves but also their delivery solutions described in the detected vulnerability information to be checked with regard to application and availability. This results in greater flexibility and efficiency in vulnerability handling.

[0043] With the help of the CI / CD pipeline and the tests defined in the pipeline, the functional capabilities of the performed changes to the software components can be ensured.

[0044] Furthermore, the corresponding production environment can be tested by the deployment of the provided adaptation with regard to the use of the defined weak spot solutions. The test results can then be fed back to the build pipeline.

[0045] Overall, software security is improved.

[0046] Other possible implementations of the present invention also include combinations not explicitly mentioned of features or embodiments described above or below with respect to the embodiments. Here, those skilled in the art will also add individual aspects as improvements or supplements to the corresponding basic forms of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Further advantageous embodiments and aspects of the invention are the subject matter of the dependent claims of the invention and of the exemplary embodiments described below. In addition, the invention is explained in more detail based on preferred embodiments with reference to the drawings.

[0048] Figure 1 A flow chart showing method steps of a first specific embodiment of a method for updating a software component;

[0049] Figure 2 a block diagram illustrating software and hardware components and processes used according to a second embodiment of a method for updating a software component; and

[0050] Figure 3 A flow chart with method steps of a second specific embodiment of a method for updating a software component is shown. DETAILED DESCRIPTION

[0051] In the figures, identical or functionally identical elements have been provided with the same reference symbols unless otherwise indicated.

[0052] exist Figure 1A schematic flow chart for software updating is shown in FIG. Typically, new software components, ie software updates, are deployed by compiling, testing and merging software components or applications, wherein deployment information is taken into account. According to the prior art, descriptions of weaknesses of software components are not included in the deployment information.

[0053] In order to ensure the safe operation of the software component, for example in the processing environment of an automation network, in a first step A1, deployment information for the software component is retrieved. The deployment information contains information about program components of the software component. If the software component exists as a software container image, the program components are, for example, package information, binary files, libraries and / or configuration data. The configuration data, for example, determine the access rights of the software component.

[0054] In a subsequent step A2, at least one program component is checked to see whether it has an exploitable vulnerability and, if necessary, the program component is identified. The check can be derived from the specification in the deployment information and / or from scan results from a search of the software container image, for example, by a vulnerability scanner. It is also conceivable that the presence of the vulnerability is read from a vulnerability database.

[0055] If no vulnerability is found based on the new software container image and / or the vulnerability database, and the key vulnerability information cannot be derived from the deployment information, the software component is tested, released to the repository and provided to the production environment. Then step A4 (see below) is directly executed.

[0056] If a weak link is found, then in step A3, runtime restrictions are specified for the program component with the weak link. For example, the parameter output or transfer of the software component to be updated to other software components is restricted to prohibit undesired function retrieval or interface release. The runtime restrictions are described by runtime restriction information attached to the deployment information.

[0057] Finally, in step A4, the deployment of the software component is performed, wherein the deployment information that has been changed or adapted to the identified weak link situation is taken into account.During the execution of the software component, the software component is then subjected to runtime restrictions according to the runtime restriction information.

[0058] In this context, weaknesses are eliminated or their potential for exploitation is reduced without having to wait for a new software component to be released. This approach is particularly useful for reducing the risk of damage from zero-day vulnerabilities or their exploitation.

[0059] The advantage of the proposed solution is that, in contrast to common vulnerability scanners that only detect vulnerabilities in container images, the deployment information associated with the image is checked within the CI / CD pipeline. Thus, clearly defined measures for (temporarily) limiting the vulnerability can be implemented. Furthermore, if protection measures have been implemented, e.g. process privileges have been revoked, this can be identified based on the deployment information, which may contain vulnerability information. The vulnerability information and / or runtime restriction information attached to the deployment information can also indicate whether the detected vulnerability can be exploited at all in the context of the software component.

[0060] The method for securely running software components can, for example, enable secure further operation of a processing environment after a software component update that uncovers a zero-day exploit vulnerability. Operation is understood in particular to be the execution of software components that interact with each other in a runtime environment.

[0061] According to the following Figure 2 and 3 A second embodiment of a method for updating a software component is explained. Here, Figure 1 shows the components involved in the method and their interactions, and Figure 3 A communication diagram is shown.

[0062] The second embodiment is based on a CI / CD pipeline with a vulnerability scanner 2 , a code repository 3 , a build pipeline 4 , a registry 5 , a merge database 6 and a runtime environment 7 . Figure 1 Other components of the processing system 1 are shown, which may be implemented as functionalized hardware or software services. The orchestrator 8 manages T3 the runtime environment 7 for instantiating T4 software containers 13. The weakness scanner 2 is communicatively coupled to the weakness database 10 and the cache memory 9. The weakness scanner 2 uses T5 the weakness information from the weakness database 10 and writes its scan results into the cache memory 9 or reads T7 its scan results from the cache memory 9.

[0063] The code repository 3 manages and maintains the TI deployment information 11. The container registry 5 provides software container images 12 respectively (step T2). The merge request entered by the vulnerability scanner 2 is identified and stored in the merge database 6, and the merge request is used and evaluated by the build pipeline 4 T6.

[0064] The aspects and steps described below may be performed when updating a software container image, ie, when releasing a new version of a base software component.

[0065] Assume that the vulnerability scanner 2 has access to the object to be searched or analyzed, in the example considered the software container image or container mirror, the package information, binaries, libraries and configuration files contained therein. This can be done directly (step S2) or by searching the vulnerability database 10.

[0066] In step S1 , the scanning process of the deployment configuration including the deployment information 11 may be an integral part of the build pipeline 4 , but may alternatively also be or be an outsourced process that is performed regularly.

[0067] The software container image 12 referenced in the deployment configuration or information 11 is searched by the scanner 2 in the registry 5 in step S2, which is referenced in the deployment information 11 for the software component to be updated (step S2). During the scanning process, the components or program components running in the software container image are identified by accessing the package manager or by comparing binary signatures. The found components are compared with the vulnerability database 10, whereby existing known vulnerabilities can be identified.

[0068] Since the same software container image, program component or binary component can be referenced multiple times in one deployment through different deployment configurations, the generated scan results are preferably stored in the cache memory 9 (step T7). For example, the scanner 2 stores in the configuration file: at what point in time a rescan of the container image should be performed, or how old the list of vulnerable software components is allowed to be.

[0069] In the CI / CD pipeline, images and binaries can be created by a translation process, or components generated elsewhere can be referenced. As long as these are only referenced and used in other pipelines, this information can be stored in the configuration file for the scanner 2. Here, it can also be stored in the configuration file for the vulnerability scanning process or the scanner 2: in which other pipeline the image was generated. The scanner 2 then evaluates this information during the corresponding runtime.

[0070] If the weakness cannot be eliminated by a software upgrade, because the image is not built in the stored CI / CD pipeline, for example, or because a patch has not yet been defined or an updated software component with a patch is not yet available, the transitional solution defined in the vulnerability database 10 is reported back to the CI / CD pipeline by the scanner 2. This occurs via a merge request S3, which is recorded S4 in the merge database 6. As a transitional solution for the corresponding weakness, runtime restrictions are set, such as restrictions on the privileges of the software component. In particular, the runtime constraints are by means of assigning special Seccomp profiles or Linux capabilities defined to minimize the attack surface to revoke the process permissions of the runtime user, and assigning special installation options to the file system mounted for the instance. This is achieved by changing the deployment information updated in step S6. The build pipeline 4 started by the code repository in step S5 adapts the deployment information or deployment configuration accordingly.

[0071] The build pipeline 4 then generates in step S7 a container image or container image 12 of the software component to be updated, which is stored S8 by the registry 5. After testing S9 the software component, deployment may be performed S10.

[0072] Additionally, exploitation of weaknesses can be prevented by defining adapted mandatory access control profiles. Another possibility is to define corresponding configuration settings for the software components introduced with the deployment, so that parameter checking is ensured for passed parameters and correspondingly structured calls are identified and blocked by means of regular expressions.

[0073] Runtime restrictions are made by opening a merge request with the proposed runtime adaptation in the pipeline 4. A runtime adaptation or runtime restriction in this case can be, for example, the revocation of certain permissions, which are automatically proposed as an adaptation in the deployment configuration 11. The proposed changes can be checked by the developer or, when using automatic merging, by means of (semi-)automatic unit and integration tests.

[0074] An automatically generated merge request that requires runtime constraints to be enforced to prevent the exploitation of weaknesses in the own CI / CD pipeline extends the defined runtime constraints to the deployment information 11. The merge request can be implemented automatically, semi-automatically (upon successful traversal of the tests) or manually by the operator of the CI / CD pipeline. It is also conceivable that the merge request is implemented either manually, using the described semi-automatic method, or automatically, depending on the criticality of the detected weaknesses. The behavior of the system is defined by the person responsible for the CI / CD pipeline, for example in a configuration file.

[0075] Deployment parameters and configuration options introduced by the scanner 2 are marked accordingly for traceability at the time of the merge and referenced together with the mentioned weaknesses. The reference can be performed via corresponding comments in the merge history.

[0076] Only when the vulnerability has been eliminated by introducing the corresponding patch and can no longer be detected, another merge request is created by the scanner 2 in step S3. For this purpose, a reference is made to the scanner 2 in the outsourcing database 6 as to which merge requests were executed for deployment due to the detected vulnerability. The ID of the merge request is associated with the vulnerability and the deployment configuration referenced thereby. In the pipeline 4, a check is made at each subsequent scan whether the referenced vulnerability is still identified and thus the conditions for the runtime restriction are still met. If this is no longer the case, the restriction can be cancelled by generating a revocation merge request.

[0077] As long as the build process 4 of the image 12 occurs within its own CI / CD pipeline, it is conceivable that the image 12 is translated with altered compilation operations (eg using Intel GET / Clang CFI to mitigate, for example, ROP attacks).

[0078] Furthermore, it is possible to temporarily relieve the basic runtime platform 7, 8 of new requirements or special hardware requirements. In an orchestration cluster, it is conceivable that, within the scope of creating an adapted deployment configuration, special tags are assigned to the generated images or deployment information, so that in an orchestrated container environment the orchestrator 8 can automatically select the correct target platform 7 or can check whether the newly introduced deployment can run on the platform at all.

[0079] If temporary adaptation of privileges and configuration settings is applied by runtime restriction information contained in the deployment information, the required functional tests are performed within the build pipeline 4 (step S9). If these functional tests fail, the development team is notified. It is possible that, manually defined by the developer, specific identified vulnerabilities should not be eliminated by privilege adaptation (e.g., by reference with a CVE number or by time restrictions) in order to maintain the functional capabilities of the application managed in the CI / CD pipeline.

[0080] In order to exclude the exploitation of weaknesses on the production environment, the deployment configuration used on the production environment can be compared by the scanner 2 (step S11). The deployment configuration can be determined by the scanner 2 either by querying the orchestrator 8 or by directly accessing the runtime environment 7. If deviations from the deployment are determined in the CI / CD pipeline, the deviations can also be reported to the CI / CD pipeline, for example via corresponding warnings or events or problems. Thus, the scanning process can also be performed not only within the pipeline within the scope of the build process 4 or as a periodic scan.

[0081] Once an image or a software component used in the pipeline no longer has a vulnerability, the configuration changes introduced by the scanner 2 can be automatically or manually undone depending on the configuration selected in the CI / CD pipeline, since the changes introduced by the scanner have been referenced with the corresponding vulnerability.

[0082] By using the deployment configuration data, the weak links are automatically neutralized until patches for the involved software components are available.

[0083] Although the present invention has been described in terms of embodiments, the present invention may be modified in various ways. Although the examples have been explained in terms of software containers, software components implemented in different ways may also be updated according to the method. Although it is said that the vulnerability scanner searches through the software image, this also means that the vulnerability scanner retrieves vulnerability information about the software image in the vulnerability database.

Claims

1. A method for securely running a software component, comprising the following steps: Retrieving (A1) deployment information for a software component, wherein the deployment information (11) includes information about program components of the software component and its runtime configuration; Checking (A2) whether at least one program component has a weak link and identifying the program component; Determining (A3) runtime constraints on program components identified as vulnerable; inserting (S6) runtime constraint information into deployment information (11) for the software component; and The deployment of the software component is performed (A4) according to the deployment information (11), wherein runtime restrictions are imposed on the software component according to the runtime restriction information when the software component is executed.

2. The method according to claim 1, characterized in that: The software component is implemented as an instance of a software container (13), and the corresponding software container image (12) includes package information, binary files, libraries and configuration data as program components.

3. The method according to claim 2, characterized in that The deployment comprises creating (S7, S8) an adapted software container image (12) for the software component according to the deployment information (11) supplemented with runtime constraints.

4. The method according to claim 3, characterized in that Prior to deployment (A4, S10), the adapted software container image (11) is functionally verified (S9) in a secure processing environment (3).

5. The method according to any one of claims 1 to 4, characterized in that The software components are deployed (A4, S10) into a runtime environment (7, 8).

6. The method according to any one of claims 1 to 5, characterized in that The deployment information (11) references one or more software container images (12).

7. The method according to any one of claims 1 to 6, characterized in that Runtime constraint information is inserted (S6) via a merge request (S3, S4) to a build pipeline (4) that causes an update of a software component.

8. The method according to any one of claims 1 to 7, characterized in that Verifying (A2) whether at least one program component has a vulnerability comprises searching (S1) the deployment information (11) and / or scanning (S2) the software container image (12).

9. The method according to any one of claims 1 to 8, characterized in that The runtime restrictions include access rights restrictions and / or restrictions on the export of passed parameters or function calls to other software components.

10. The method according to any one of claims 1 to 9, further comprising: The deployment information (11) is supplemented (S3) with vulnerability information, which is assigned to the identified software component and / or the identified program component having a vulnerability, wherein the vulnerability information includes in particular the existence of the vulnerability and / or the elimination of the vulnerability by runtime restrictions, and / or Vulnerability information assigned to the identified software components and / or program components identified as having vulnerabilities is stored in a vulnerability database (10).

11. The method according to any one of claims 1 to 10, further comprising: Searching (S1) for vulnerability information assigned to the software component and / or the identified program component in the deployment information for the software component; and The software components are deployed according to the weak link information (S10, S11).

12. The method according to claim 10 or 11, characterized in that: Check (A2) whether at least one process component has a weak link, among other things: The vulnerability information is stored as configuration data in a vulnerability database (10) for use in the vulnerability scanning process.

13. The method according to any one of claims 1 to 12, characterized in that Weak points include the possibility of passing unchecked parameters and / or function calls by the software component.

14. A method for operating a processing system (1), the processing system being configured to provide one or more software functions, wherein a plurality of interacting software components are executed in a runtime environment (7), comprising: One of the software components is operated according to the method according to any one of claims 1 to 13.

15. A computer program product comprising instructions which, when executed by one or more computers, cause the one or more computers to perform the method according to any one of claims 1 to 14.

Citation Information

Patent Citations

  • Software third-party component vulnerability emergency response system and method based on big data

    CN110909363A

  • Safety and compliance treatment method suitable for open source component

    CN112800430A

  • Detecting security risks related to a software component

    CN112868007A

  • Docker mirror image analysis method and device, electronic equipment and storage medium

    CN113065125A

  • Static detection of vulnerabilities in base images of software containers

    US20170109536A1