Methods and systems for generating core dumps in user equipment

By classifying memory data in user equipment and using encryption keys to generate and reconstruct core dumps, the problem of sensitive data exposure in existing technologies is solved, and the security and confidentiality of core dumps are improved.

CN114579337BActive Publication Date: 2026-11-10SAMSUNG ELECTRONICS CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111461194.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-12-01
Filing Date
2021-12-01
Publication Date
2026-11-10
Estimated Expiration
2041-12-01

AI Technical Summary

Technical Problem

Existing technologies pose a risk of exposing sensitive data when generating core dumps, and lack effective encryption and decryption mechanisms, making modem baseband processors vulnerable to attacks and difficult to protect confidential information.

Method used

By detecting triggers in user equipment to generate a core dump, classifying memory data as read-write and read-only data, generating a partial core dump, and using an encryption key to encrypt sensitive data, a complete core dump can be reconstructed.

Benefits of technology

It enables the protection of sensitive data in the event of a system crash, reduces the risk of hacker attacks, and ensures the security and confidentiality of the core dump.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114579337B_ABST
    Figure CN114579337B_ABST
Patent Text Reader

Abstract

A method for generating a core dump in a user equipment (UE) may include using at least one processor to detect a trigger, the trigger including instructions for generating a core dump of the UE. The method may further include using the at least one processor to classify data stored in the UE's memory into read-write (RW) data or read-only (RO) data. The method may further include using the at least one processor to generate a partial core dump based on the RW data in the memory.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications

[0002] This application claims priority to Indian Provisional Patent Application No. 202041052295, filed on December 1, 2020, with the General Office of Patents, Designs and Trademarks (CGPDTM), the entire contents of which are incorporated herein by reference. Technical Field

[0003] Various example embodiments generally relate to core dumps, and more specifically to methods, apparatus, systems and / or non-transitory computer-readable media for generating core dumps in user equipment (UE). Background Technology

[0004] Traditionally, modem processors are responsible for providing wireless communication and connectivity in smartphones across a range of technologies. Increased digitization has led to smartphones being used for confidentiality-critical communications such as banking, one-time password-based authentication, sending / receiving confidential data, and digital rights management (DRM), much of which uses modem basebands for switching over a network. This increases the need for and / or requirement for stronger security in digital communications, while also increasing the risk of exposing these critical security credentials to hackers through reverse engineering, eavesdropping, or malware attacks. Most documented cyberattacks are discovered after gaining significant knowledge about the design and operation of computer and / or network systems. A core dump is one such attack vector (e.g., a cyberattack vector) that exposes information that allows cyber intruders to discover vulnerabilities in computer and / or network systems.

[0005] A core dump contains the current execution state of a computer system, currently used code (e.g., program code, computer-readable instructions, etc.), static strings, and data residing in memory in the event of a computer system failure. In most embedded systems, all code resides in memory at all times. There is no on-demand loading of code into memory. Therefore, a core dump of such a system will contain all code stored in memory. Most released consumer devices will have the option to collect core dumps for debugging purposes. One option is to not allow core dumps to be captured on consumer devices. However, even after extensive testing before release, some issues may only appear after the device reaches the customer. In such cases, a core dump is still expected and / or needed to debug and fix the problem.

[0006] Easy access to the core dump facilitates attacks on modem baseband processors. Reports indicate that most reverse engineering of cellular modems is performed by accessing the contents of the modem baseband processor's core dump. Access to the core dump facilitates the identification of software vulnerabilities, security flaws, and / or errors. Malicious programs injected by exploiting these vulnerabilities help hackers gain control of the modem and / or extract confidential information that they might otherwise be unable to access.

[0007] The encryption and decryption of random access memory (RAM) dumps for Windows virtual machines are discussed in related fields. A system is configured for a Windows virtual machine. It encrypts all contents of the RAM. In the systems described above, the user needs a public / private key pair.

[0008] Another related system involves encrypting portions of RAM in which the contents are encrypted during system runtime, thereby creating a secure area where sensitive information can reside. However, this system does not address how to decrypt the encrypted information and / or perform a core dump in the event of a system crash.

[0009] Another system in this related field involves "hiding" sensitive areas of a RAM dump by replacing sensitive data with random data or by encrypting sensitive areas using a "dynamic key algorithm." However, this system does not include protection code. In this system, sensitive data is marked differently, requiring developers to mark every variable / structure / allocation as sensitive. Solutions proposed in this related field require changes to the compiler and linker so that sensitive areas are identified and marked for each source file. The object file structure must then also be modified.

[0010] The runtime overhead associated with allocating and releasing sensitive data during runtime increases. The hiding of sensitive data is achieved using existing random replacement algorithms or existing encryption algorithms. However, the relevant domain does not publicly disclose the retrieval of sensitive data, and the operation of hiding sensitive data in the relevant domain is a one-way process. Scanning modules exist that scan RAM to find sensitive data.

[0011] Other related fields describe the encryption and decryption of object data in core dumps. One related field discloses a privacy-preserving module connected to a signal processor. It does not skip read-only (RO) areas in the core dump after a hash / CRC (Cyclic Redundancy Check) check. It does not use asymmetric encryption. Furthermore, there is no selective encryption of portions of RAM. Additionally, the privacy-preserving module locates sensitive data in RAM.

[0012] A solution is expected and / or needed to overcome the above-mentioned shortcomings. Summary of the Invention

[0013] This summary provides a simplified overview of the selected concepts further described in the detailed embodiments. This summary is not intended to identify key or essential inventive concepts of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter. For the purposes of this disclosure, various exemplary embodiments implemented and broadly described herein depict methods, apparatus, systems, and / or non-transitory computer-readable media for generating core dumps in a UE.

[0014] Based on some exemplary embodiments of the present invention, a method for generating a core dump in a UE is disclosed. The method may include: using at least one processor, detecting a trigger including instructions for generating a core dump in the UE; using the at least one processor, classifying data stored in the UE's memory into read-write (RW) data or read-only (RO) data; and using the at least one processor, generating a partial core dump based on the RW data in the memory.

[0015] According to some exemplary embodiments of the present invention, a method for reconstructing a complete core dump is disclosed. The method may include: using at least one processor, receiving a trigger including instructions for generating a complete core dump of a user equipment (UE); using the at least one processor, obtaining read-only (RO) data from a desired partial core dump file, the desired partial core dump file being at least partially encrypted; using the at least one processor, writing the RO data to an output file; using the at least one processor, obtaining read-write (RW) data from the desired partial core dump file; and using the at least one processor, writing the RW data to the output file to reconstruct the complete core dump.

[0016] According to some exemplary embodiments of the present invention, a system for generating a core dump in a UE is disclosed. The system may include: at least one processor configured to execute computer-readable instructions to perform the following operations: detecting a trigger including instructions for generating a core dump in the UE; classifying data stored in the UE's memory into read-write (RW) data and read-only (RO) data present in the UE's memory; and generating a partial core dump based on the RW data in the UE's memory.

[0017] According to some exemplary embodiments of the present invention, a decryption apparatus for reconstructing a complete core dump is disclosed. The decryption apparatus may include: at least one processor configured to execute computer-readable instructions to perform the following operations: receiving a trigger including instructions for generating a complete core dump of a user equipment (UE); obtaining read-only (RO) data from a desired partial core dump file, the partial core dump file being at least partially encrypted; writing the RO data to an output file; obtaining read-write (RW) data from the desired partial core dump file; and writing the RW data to the output file to reconstruct the complete core dump.

[0018] These aspects and advantages will become clearer from the following detailed description taken in conjunction with the accompanying drawings and the claims. Attached Figure Description

[0019] Figure 1 A flowchart illustrating an operation for generating a core dump in a UE, depicting at least one example embodiment of a concept according to the present invention;

[0020] Figure 2A A schematic block diagram of a system for generating a core dump in a UE, according to at least one example embodiment of the concept of the present invention, is shown.

[0021] Figure 2B A schematic block diagram illustrating a decryption entity for decrypting an encrypted portion, according to at least one example embodiment of the present invention;

[0022] Figure 3A A flowchart illustrating an operation for generating a core dump according to at least one example embodiment of the concept of the present invention is shown;

[0023] Figure 3B A flowchart illustrating an operation for reconstructing a complete core dump according to at least one example embodiment of the concept of the present invention is shown;

[0024] Figure 4 A flowchart illustrating an operation for reconstructing a complete core dump according to at least one example embodiment of a concept based on the present invention is shown.

[0025] Figure 5 A graphical representation illustrating the entropy of a typical core dump depicting at least one exemplary embodiment of the concept according to the present invention; and

[0026] Figure 6 A graphical representation of a core dump depicting at least one example embodiment of an entropy-fully encrypted core dump according to a concept of the present invention is shown.

[0027] Furthermore, those skilled in the art will understand that the elements in the accompanying drawings are shown for simplicity and do not necessarily need to be drawn to scale. For example, the flowcharts illustrate the methods according to the most prominent operations involved to aid in understanding at least one exemplary embodiment of the inventive concept. Additionally, depending on the construction of the device, one or more components of the device may be represented in the drawings by conventional symbols, and the drawings may show only those specific details relevant to understanding exemplary embodiments of the inventive concept, so as not to obscure the drawings with details that are obvious to those skilled in the art who will benefit from the description herein. Detailed Implementation

[0028] For the purpose of facilitating an understanding of the principles of one or more exemplary embodiments of the inventive concept, reference will now be made to the embodiments shown in the accompanying drawings, and they will be described using specific language. However, it will be understood that this is not intended to limit the scope of the exemplary embodiments, and such changes and further modifications in the illustrated systems, as well as such further applications of the principles of the exemplary embodiments shown herein, are considered to be commonly conceived by those skilled in the art to which the inventive concept relates.

[0029] Those skilled in the art will understand that the foregoing general description and the following detailed description are explanations of one or more exemplary embodiments of the inventive concept and are not intended to limit it.

[0030] References to "one aspect," "another aspect," or similar language throughout this specification indicate that a particular feature, structure, or characteristic described in connection with the exemplary embodiments is included in at least one exemplary embodiment of the inventive concept. Therefore, the appearance of phrases such as "in at least one exemplary embodiment," "in another exemplary embodiment," and similar language throughout this specification may, but does not necessarily, refer to the same exemplary embodiment.

[0031] The terms “comprising,” “including,” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process or method that includes a series of operations does not only include those operations, but may include other operations not expressly listed and / or inherent to such process and / or method. Similarly, without further constraints, the inclusion of one or more devices, subsystems, elements, structures, and / or components following “comprising” does not exclude the presence of other devices, subsystems, elements, structures, components, additional devices, subsystems, elements, structures, and / or components.

[0032] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the inventive concept belongs. Examples of systems, methods, apparatuses, and / or non-transitory computer-readable media provided herein are illustrative only and are not intended to be limiting.

[0033] For the sake of brevity, the first digit of the reference numeral for each component in the example embodiment indicates the drawing number, where the corresponding component is shown. For example, reference numerals beginning with the digit "1" at least... Figure 1 The reference numerals beginning with the number "2" are shown in Figure 2, and so on.

[0034] Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0035] Figure 1 A flowchart 100 illustrates an operation method for generating a core dump in a UE, according to at least one example embodiment of a concept based on the present invention.

[0036] In operation 102, the method includes detecting a trigger for generating a core dump, etc. According to at least one example embodiment, the trigger may be generated by a UE (such as...). Figure 2A The examples include commands, faults, anomalies, etc. sent and / or generated by UE 203a, etc., but the example embodiments are not limited thereto.

[0037] In operation 104, the method includes identifying read-write (RW) data and read-only (RO) data, etc., that exist in the random access memory (RAM) of the UE.

[0038] In operation 106, the method includes generating a partial core dump based on RAM-based RW data.

[0039] Combining Figure 2A Operations 102 through 106 will be discussed in more detail.

[0040] Figure 2AA schematic block diagram 200a illustrates a system 202a for generating a core dump in a UE 203a, according to at least one exemplary embodiment of the present invention. In at least one exemplary embodiment, system 202a and / or UE 203a may be implemented in one or more electronic devices such as smartphones, tablets, laptops, desktop computers, workstations, servers, wearable devices, network devices, other smart devices, Internet of Things (IoT) devices, game consoles, navigation devices, autonomous devices (e.g., autonomous vehicles), cloud devices, virtual reality and / or augmented reality devices, robotic devices, electronic healthcare devices, etc., but the exemplary embodiments are not limited thereto. In at least one exemplary embodiment, system 202a may be implemented in a single device and / or in a distributed manner across multiple devices, but the exemplary embodiments are not limited thereto. According to at least one exemplary embodiment, system 202a may be part of UE 203a, or may be a separate electronic device connected to UE 203a via a wired interface and / or a wireless interface, etc.

[0041] In at least one example embodiment, system 202a may include at least one processor 204a, memory 206a (storage device), and / or data 208a, etc., but the example embodiment is not limited thereto. For example, system 202a may include more or fewer components, such as multiple processors 204a, multiple memories 206a, a baseband modem processor, a wired network interface, a wireless network interface, a display device, a separate data storage device (e.g., storage space), etc. According to some example embodiments, data 208a may be stored in memory 206a, but the example embodiment is not limited thereto. For example, data 208a may be stored in a separate data storage device, etc. Similarly, UE 203a may include at least one processor 205a and / or memory 207a (e.g., storage device), etc., but the example embodiment is not limited thereto.

[0042] In at least one example embodiment, processors 204a and / or 205a may be a single processing unit (e.g., processing circuitry, etc.) or multiple processing units, wherein all processing units may include multiple computing units. Processors 204a and / or 205a may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any hardware device that manipulates signals based on operating instructions. For example, processors 204a and / or 205a (e.g., processing circuitry) may include: hardware such as processors, processor cores, logic circuits, storage devices, etc.; hardware / software combinations such as executing software and / or executing at least one processor core with an arbitrary instruction set; or combinations thereof. For example, processing circuitry may more specifically include, but is not limited to, field-programmable gate arrays (FPGAs), programmable logic units, application-specific integrated circuits (ASICs), system-on-a-chip (SoCs), etc. Among other capabilities, processors 204a and / or 205a are configured to acquire and execute, but are not limited to, computer-readable instructions and data stored in memories 206a and / or 207a.

[0043] According to some example embodiments, at least one processor 204a may be configured to run and / or execute a boot-up procedure stored in the UE 203a. In at least one example embodiment, the boot-up procedure may include generating a checksum based on RO data present in and / or stored in RAM 207a of the UE 203a; however, the example embodiments are not limited to this. For example, the boot-up procedure may be stored in BIOS memory and / or the ROM of the UE, stored on a network device, stored on a removable disk, etc. When generating the checksum, the processor 204a may be configured to store the checksum in memory 206a. In at least one example embodiment, the checksum may be stored in a reserved area of ​​RAM in memory 206a (e.g., a desired area, a target area, etc.); however, the example embodiments are not limited to this.

[0044] According to some example embodiments, processor 204a can be configured to generate checksums associated with RO data by segmenting RO data into several RO data segments (e.g., multiple RO data segments). Furthermore, processor 204a can be configured to generate several checksums associated with and / or corresponding to the several RO data segments (e.g., generating multiple checksums), etc. In at least one example embodiment, processor 204a can be configured to store several checksums (e.g., multiple checksums) into a reserved area of ​​RAM, but the example embodiments are not limited thereto.

[0045] According to at least one example embodiment, processor 204a can be configured as follows: Figure 1The detection of triggers (e.g., instructions, faults, exceptions, etc.) related to the process of generating a core dump, as discussed in operation 102, is described. In at least one example embodiment, triggers may be detected during startup, during normal execution of system 202a, and / or when one or more hardware and / or software errors experienced by UE 203a and / or system 202a occur, but the example embodiments are not limited thereto. Upon detection of a trigger, processor 204a may identify and / or classify data residing in RAM 207a and / or other memory and / or data storage devices (e.g., flash memory, SSD, hard disk drive, etc.) of UE 203a. In at least one example embodiment, as in Figure 1 As discussed in Operation 104, data stored in RAM can be identified and / or classified as read-write (RW) data and / or read-only (RO) data, etc.

[0046] According to some example embodiments, processor 204a can be configured as follows: Figure 1 The generation of a partial core dump based on the RW data of RAM 207a (and / or other memory) of UE 203a, as discussed in Operation 106, allows RW data to be added to the partial core dump. According to some example embodiments, only the RW data of RAM can be added to the partial core dump, but the example embodiments are not limited thereto. For example, the RW data and / or RO data added to the partial core dump can be desired data that has been selected, requested, known, and / or identified as sensitive data, confidential data, technical data, etc.

[0047] In addition to generating a partial core dump, processor 204a can be configured to derive and / or generate encryption keys. To derive and / or generate encryption keys, processor 204a can be configured to generate a random number r (and / or a pseudo-random number, etc.), but the example embodiments are not limited thereto. In at least one example embodiment, the random number r can be referred to as the UE's private key. In at least one example embodiment, the private key "r" can be referred to as "PrivD". In at least one example embodiment, processor 204a can be configured to compute the public key "PubD" using, for example, an ECC operation as shown below, but the example embodiments are not limited thereto.

[0048] PubD = PrivD.G

[0049] Where G is the point where the elliptic curve is generated.

[0050] Furthermore, according to at least one example embodiment, processor 204a can be configured to derive and / or generate a shared secret value “S” using, for example, the following ECC operation, but the example embodiment is not limited thereto.

[0051] S = PrivD.PubH

[0052] In at least one example embodiment, “Pubh” may be pre-generated and exist in the UE, but the example embodiment is not limited thereto.

[0053] Furthermore, processor 204a can be configured to feed "S" into, for example, a key derivation function (KDF) to derive and / or generate a symmetric key "k" for an encryption algorithm. In at least one example embodiment, the encryption algorithm may be a symmetric key encryption algorithm as shown below, but the example embodiment is not limited thereto.

[0054] k = KDF(S)

[0055] In at least one example embodiment, processor 204a can be configured to determine the failure of the encryption technique. As an example, the encryption technique may fail due to a system crash or other reasons prior to generating the symmetric key. As another example, the encryption technique may fail due to a system crash or other reasons occurring during ECC operation.

[0056] According to at least one example embodiment, upon determining a failure of the encryption technique, processor 204a can be configured to implement a fallback (e.g., alternative key generation) mechanism. In at least one example embodiment, processor 204a can be configured to generate a symmetric key (e.g., an alternative symmetric key, etc.) using a KDF based on, for example, a symmetric key encryption algorithm with a salted input, when a system crash occurs before or during ECC operation, but the example embodiment is not limited thereto. According to at least one example embodiment, the salt input can be the system time and RO region checksum of system 202a, but the example embodiment is not limited thereto.

[0057] Salt = T | Checksum Value

[0058] Where T = current system time, and ChecksumValue = checksum of the RO region calculated at startup time. '|' indicates concatenation.

[0059] k = KDF(Salt)

[0060] Furthermore, the processor 204a can be configured to send the salt input along with the core dump, so that a symmetric key can be generated for decryption, etc.

[0061] According to some example embodiments, upon detecting a trigger (e.g., instruction, fault, exception, etc.) and generating an encryption key, processor 204a can be configured to perform a verification operation on a plurality of checksums (e.g., multiple checksums). In at least one example embodiment, the verification operation may include, but is not limited to, comparing the plurality of checksums with a plurality of checksums stored in a reserved area of ​​RAM in memory 206a (e.g., comparing the multiple checksums with multiple checksums previously generated (e.g., after a UE startup operation) and stored in a reserved area of ​​RAM). In at least one example embodiment, processor 204a can be configured to perform a comparison based on the value of each of the plurality of checksums, such that the value is compared with another value associated with each of the plurality of checksums previously stored in RAM in memory 206a. During the comparison, processor 204a may be configured to identify one or more checksums among the plurality of checksums that failed the verification operation (e.g., identifying and / or determining whether a checksum is valid or invalid).

[0062] According to some example embodiments, upon identifying one or more checksums that have failed verification, processor 204a may be configured to append one or more RO data fragments associated with said one or more checksums to a partial core dump. In at least one example embodiment, processor 204a may be configured to encrypt one or more RO fragments by applying a desired and / or predefined cryptographic technique. In at least one example embodiment, the desired and / or predefined encryption technique may be a symmetric-key encryption algorithm, but the example embodiments are not limited thereto.

[0063] Furthermore, the key "k" can be used to encrypt sensitive portions of the dump. In at least one example embodiment, the sensitive portions may include one or more RO data segments encrypted using a symmetric key encryption algorithm. In at least one example embodiment, the processor 204a may be configured to send the encrypted core dump along with the public key "PubD" during encryption, but the example embodiments are not limited thereto.

[0064] When encrypting one or more RO data segments, processor 204a can be configured to append one or more encrypted RO data segments to a portion of the core dump. In at least one example embodiment, one or more encrypted RO data segments can be interchangeably referred to as one or more encrypted portions, etc. In at least one example embodiment, processor 204a can be configured to append one or more encrypted RO data segments in a random order, but is not limited thereto. Furthermore, by encrypting RO data segments using the encryption method described above, the ability of malicious actors to access potentially usable UE sensitive data, confidential data, technical data, etc., in the core dump can be reduced and / or diminished.

[0065] The memory 206a may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory (such as static random access memory (SRAM) and / or dynamic random access memory (DRAM)) and / or non-volatile memory (such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk and / or magnetic tape).

[0066] Among other things, data 208a also serves as a repository for storing data processed, received, and / or generated by one or more of the processor 204a and / or memory 206a. One or more of the aforementioned components of system 202a, written in a non-limiting manner, may send and / or receive data, for example, using one or more input / output ports, one or more buses, and one or more communication units (e.g., communication processors, network interfaces, etc.), but the example embodiments are not limited thereto.

[0067] Figure 2B A schematic block diagram 200b illustrates a decryption entity 202b (e.g., decryption device, etc.) for decrypting an encrypted section according to at least one exemplary embodiment of the present invention. According to some exemplary embodiments, the decryption entity 202b may include at least one processor 204b, memory 206b, and / or data 208b, etc., but the exemplary embodiments are not limited thereto; for example, it may include more or fewer constituent components. In at least one exemplary embodiment, the processor 204b may be a single processing unit (e.g., processing circuitry, etc.) or multiple processing units, wherein all processing units may include multiple computing units. The processor 204b may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any hardware device that manipulates signals based on operating instructions. For example, the processor 204b (e.g., processing circuitry) may include: hardware such as a processor, processor core, logic circuitry, storage device, etc.; a hardware / software combination such as at least one processor core executing software and / or executing any instruction set; or a combination thereof. For example, the processing circuitry may more specifically include, but is not limited to, field-programmable gate arrays (FPGAs), programmable logic units, application-specific integrated circuits (ASICs), and system-on-a-chip (SoCs). Among other capabilities, processor 204b is configured to fetch and execute, but is not limited to, computer-readable instructions and data stored in memory 206b.

[0068] In at least one example embodiment, processor 204b may be configured to identify one or more encrypted portions from several data portions (e.g., data segments, memory sections, etc.). In at least one example embodiment, one or more encrypted portions may include at least one of RO data segments and RW data segments, but the example embodiments are not limited thereto.

[0069] In at least one example embodiment, the processor 204b can also be configured to receive signals from sources such as... Figure 2A UE devices such as UE 203a receive triggers (e.g., instructions, faults, anomalies, etc.) to generate a core dump. In at least one example embodiment, to generate a core dump, processor 204b may be configured to read reserved areas in a partial core dump to obtain information related to certain portions of the partial core dump. In at least one example embodiment, processor 204b may also be configured to obtain the public key "Pubd" present in (and / or included in, stored in, etc.) the partial core dump, but the example embodiments are not limited thereto.

[0070] According to some example embodiments, processor 204b can be configured to acquire RO data from at least one desired and / or predetermined file. In at least one example embodiment, the desired and / or predetermined file may be an executable and linkable format (ELF) file, but is not limited thereto. Furthermore, processor 204b can be configured to write RO data to at least one output file, etc. In at least one example embodiment, processor 204b can be configured to acquire RW data from a partial core dump and write the RW data to an output file to create a complete core dump, etc.

[0071] Furthermore, processor 204b can be configured to decrypt one or more encrypted portions of a partial core dump, but is not limited thereto. In at least one example embodiment, one or more encrypted portions may include one or more corrupted RO data fragments, but is not limited thereto. In at least one example embodiment, processor 204b can be configured to obtain sorting information corresponding to the order of the RO data from a desired and / or predetermined location in the partial core dump (e.g., the order in which the RO data was appended to the partial core dump, etc.). Furthermore, processor 204b can be configured to reorder one or more corrupted RO data fragments based on the sorting information (e.g., reverting the order of one or more corrupted RO data fragments back to their original order, etc.). Furthermore, processor 204b can be configured to decrypt one or more encrypted corrupted RO data fragments, etc.

[0072] In at least one example embodiment, the processor 204b for decryption can be configured to obtain the UE's public key from a desired and / or predetermined location. Furthermore, the processor 204b can be configured to generate a shared key based on the obtained UE's public key and the private key of the decryption entity 202b (e.g., a private key stored in the decryption entity 202b). Additionally, the processor 204b can be configured to generate a symmetric key based on the shared key using, for example, a KDF (Knowledge, Power, and Decryption) algorithm, but the example embodiment is not limited thereto. In response to the generation of the symmetric key, the processor 204b can be configured to decrypt at least a partially encrypted partial core dump based on the generated symmetric key and a decryption algorithm.

[0073] The memory 206b may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory (such as static random access memory (SRAM) and / or dynamic random access memory (DRAM)) and / or non-volatile memory (such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk and / or magnetic tape), but the example embodiments are not limited thereto.

[0074] Among other things, data 208b also serves as a repository for storing data processed, received, and / or generated by one or more of the processor 204b and / or memory 206b, etc. One or more of the aforementioned components further written into the decryption entity 202b in a non-limiting manner may send and / or receive data, for example, using one or more input / output ports, one or more buses, and / or one or more communication units (e.g., communication processors, network interfaces, etc.), but the example embodiments are not limited thereto.

[0075] Figure 3A A flowchart 300a illustrates an operation process for generating a core dump according to at least one exemplary embodiment of the concept according to the present invention. In at least one exemplary embodiment, the core dump can be generated as follows: Figure 2A and Figure 2B The system discussed herein is generated by system 202a. In at least one example embodiment, system 202a may be incorporated into the UE, but the example embodiments are not limited thereto. Examples of UEs may include, but are not limited to, smartphones, personal computers (PCs), laptops, tablets, wearable devices, servers, network devices, other smart devices, Internet of Things (IoT) devices, game consoles, navigation devices, autonomous devices (e.g., autonomous vehicles), cloud devices, virtual reality and / or augmented reality devices, robotic devices, electronic healthcare devices, etc., but the example embodiments are not limited thereto.

[0076] During operation 302a, system 202a can execute a startup procedure for the UE.

[0077] In operation 304a, system 202a can segment the RO data existing in the RO region into several RO data fragments (e.g., multiple RO data fragments). After generating several RO fragments (e.g., multiple RO data fragments), system 202a can proceed to operation 306a.

[0078] In operation 306a, system 202a can generate several checksums associated with several RO data segments. In at least one example embodiment, each checksum may be a Cyclic Redundancy Check (CRC) value calculated for each RO data segment, but the example embodiment is not limited to this; for example, other hashing techniques may be used. In at least one example embodiment, the several checksums may be stored in a storage space (e.g., a storage device) such as memory 206a, a non-transitory computer-readable medium, etc.

[0079] During operation 308a, system 202a can detect crashes and trigger (e.g., initiate, indicate, cause, etc.) the generation of partial core dumps. Examples of crashes may include, but are not limited to, modem crashes, software system errors, hardware system errors, and / or data theft attempts.

[0080] In operation 310a, system 202a can identify data residing in the UE's RAM (and / or other memory). In at least one example embodiment, the data can be identified as read-write (RW) data and / or read-only (RO) data, etc. In at least one example embodiment, RO data may include, but is not limited to, information existing in an executable and linkable format (ELF). In at least one example embodiment, the information may include code (e.g., program code, software code, etc.), strings, and / or hard-coded / pre-stored information in binary format, etc., but the example embodiments are not limited to these.

[0081] In operation 312a, system 202a can generate partial core dumps based on RW data, so that RO data is not added to the partial core dumps.

[0082] In operation 314a, system 202a can derive an encryption key associated with a portion of the core dump, an extended encryption key associated with several checksums and several RO data segments (e.g., multiple checksums and multiple RO data segments), etc. In at least one example embodiment, generating the encryption key may include generating a random number (and / or a pseudo-random number) r. In at least one example embodiment, the random number r may be referred to as the UE's private key. In at least one example embodiment, the private key "r" may be referred to as "PrivD". Furthermore, system 202a may, for example, calculate the public key using ECC operations:

[0083] PubD = PrivD.G

[0084] Where G is the point where the elliptic curve is generated.

[0085] In addition, System 202a can export shared secret values ​​using, for example, ECC operations:

[0086] S = PrivD.PubH

[0087] Furthermore, system 202a can feed "S" into a key derivation function (KDF) to derive a symmetric key for an encryption algorithm. In at least one example embodiment, the algorithm may be a symmetric key encryption algorithm, but the example embodiments are not limited thereto.

[0088] k = KDF(S)

[0089] In at least one example embodiment, if the encryption technique is determined to be unsuccessful, for example, due to a system crash that occurs before and / or during ECC operation causing the encryption technique to fail, system 202a may use a KDF of a symmetric key encryption algorithm based on salted inputs (e.g., system time and / or RO region checksum) to generate a symmetric key.

[0090] Salt = T | Checksum

[0091] Where T = current system time, and checksum = checksum of RO region calculated at startup time. '|' indicates concatenation.

[0092] k = KDF(Salt)

[0093] In addition, system 202a can send the salt input along with the core dump, so that a symmetric key can be generated for decryption.

[0094] In operation 316a, system 202a may verify several checksums associated with several RO data segments in response to the start of core dump generation. In at least one example embodiment, verification may include comparing several checksums (e.g., the current checksum) with several other checksums (e.g., previous checksums, checksums generated during UE startup operations (such as those generated during operation 306a), checksums generated during known normal operation of the UE, etc.) previously stored in a reserved area of ​​RAM in memory 206. In at least one example embodiment, system 202a may perform the comparison based on the value of each of the several checksums (e.g., multiple checksums), such that the value is compared with another value associated with each of the several other checksums previously stored in RAM in memory 206.

[0095] In at least one example embodiment, system 202a may proceed to operation 318a if it is determined that the value associated with each of the plurality of checksums may be the same as and / or similar to another value associated with the plurality of other checksums.

[0096] In at least one example embodiment, system 202a may proceed to operation 320a if it is determined that the value associated with each of the plurality of checksums is different from another value associated with a plurality of other checksums.

[0097] In operation 318a, system 202a can skip sending a portion of the RO region to a partial core dump.

[0098] In operation 320a, system 202a can encrypt a portion of the core dump. In at least one example embodiment, encryption includes generating a random private key for the UE using cryptographic key exchange techniques, but is not limited thereto. In at least one example embodiment, system 202a can generate a public key for the UE based on the generated random private key and an asymmetric cryptographic algorithm, but the example embodiments are not limited thereto. In at least one example embodiment, after the public key is generated, system 202a can generate a shared key derived from the UE's random private key and the public key of the decryption entity. Furthermore, system 202a can generate a symmetric key based on the UE's random private key and the public key of the decryption entity 202b, but the example embodiments are not limited thereto.

[0099] Furthermore, system 202a can encrypt at least a portion of the RW data using a symmetric key to obtain at least a partially encrypted partial core dump. Additionally, system 202a can append the UE's public key at desired and / or predetermined locations within the at least partially encrypted partial core dump, but the example embodiments are not limited thereto. In at least one example embodiment, system 202a can generate an alternative symmetric key if a failure is determined during encryption of at least a portion of the RW data using a symmetric key, etc. Furthermore, when generating the alternative symmetric key, system 202a can generate the symmetric key using a KDF based on an asymmetric key encryption algorithm with system time (e.g., current system time) and RO area checksum, but the example embodiments are not limited thereto.

[0100] In at least one example embodiment, system 202a may check whether one or more security criteria (e.g., security settings, parameters, etc.) are set in the UE. In at least one example embodiment, one or more security criteria may include: active RAT information for selectively encrypting at least a portion of RW data associated with an active remote access tool (RAT); information received from one or more internal security modules (e.g., a fake base station detection module (e.g., fake base station detection code, etc.), a stack corruption detection module (e.g., stack corruption detection code, etc.), and / or a buffer overflow detection module (e.g., buffer overflow detection code, etc.)) for determining at least a portion of the RW data to be encrypted based on a higher risk assessment; information received from an application processor (AP) and / or coprocessor indicating the size of at least a portion of the RW data to be encrypted; and / or a fixed range specifying the memory addresses to be encrypted, etc. Furthermore, system 202a may encrypt at least a portion of the RW data in a partial core dump when it is determined that one or more security criteria are set in the UE, to obtain a partially encrypted partial core dump.

[0101] In operation 322a, when each of a plurality of checksums differs from another value associated with a plurality of other checksums, system 202a may append a plurality of RO data fragments to a partial core dump, etc., during encryption. In at least one example embodiment, the plurality of checksums having values ​​different from the other value may be referred to as one or more RO data fragments, but is not limited thereto. In at least one example embodiment, one or more RO data fragments may be appended to a partial core dump in a random order.

[0102] The process can be terminated when operating 324a.

[0103] Figure 3B A flowchart 300b illustrates an operation process for reconstructing a complete core dump, depicting at least one exemplary embodiment of the concept according to the present invention. In at least one exemplary embodiment, upon receiving... Figure 3A A partial core dump is generated during the generation of a full core dump, but the example embodiments are not limited thereto. In at least one example embodiment, a full core dump may be generated in response to receiving a trigger (e.g., instruction, signal, etc.) for generating a full core dump.

[0104] In operation 302b, decryption entity 202b can read reserved areas in a partial core dump to obtain information related to several parts (e.g., multiple parts) of the partial core dump.

[0105] In operation 304b, decrypting entity 202b can obtain the public key that exists (e.g., included in, appended to, etc.) in a portion of the core dump. In at least one example embodiment, the public key may be Figure 2A The term "PubD" is mentioned, but not limited to, in at least one example embodiment. In at least one example embodiment, the decryption entity 202b can use "PubD" to derive the symmetric key for decryption. In at least one example embodiment, the decryption entity 202b can derive the symmetric key using the following formula:

[0106] S = PubD.PrivH

[0107] k = KDF(S), where k = Figure 3A k is generated in the middle.

[0108] The encryption key that exists in part of the core dump is Figure 3A The key "k" is generated and sent along with a portion of the core dump for decryption, but the example implementation is not limited to this.

[0109] In operation 306b, decryption entity 202b can obtain RO data from a desired and / or predetermined file. In at least one example embodiment, the desired and / or predetermined file may be one or more of an ARM executable (AXF) file and / or an ELF format file, but the example embodiment is not limited thereto. Furthermore, decryption entity 202b can write the RO data to an output file. In at least one example embodiment, decryption entity 202b can obtain RW data from a partial core dump. Upon obtaining RW data from a partial core dump, decryption entity 202b can write the RW data to an output file to reconstruct the complete core dump.

[0110] In operation 308b, decryption entity 202b can determine whether each of the several parts of the partial core dump is encrypted. In at least one example embodiment, if it is determined that one of the several parts is encrypted, decryption entity 202b can proceed to operation 312b. In at least one example embodiment, if it is determined that one of the several parts is not encrypted, decryption entity 202b can proceed to operation 310b.

[0111] In operation 310b, decrypting entity 202b can write the portion identified as unencrypted to the output file.

[0112] In operation 312b, decryption entity 202b can decrypt one or more portions of a plurality of parts (e.g., multiple parts) that are identified and / or determined to be one or more encrypted portions. In at least one example embodiment, one or more encrypted portions may include one or more RW data fragments and / or RO data fragments from a portion of RW data encrypted based on one or more security standards. In at least one example embodiment, one or more encrypted portions may include one or more corrupted RO data fragments. In at least one example embodiment, decryption entity 202b can obtain sorting information corresponding to the order of the RO data from a desired and / or predetermined location in a partial core dump.

[0113] Furthermore, decryption entity 202b can reorder one or more corrupted RO data segments based on sorting information. Additionally, decryption entity 202b can decrypt one or more corrupted RO data segments. In at least one example embodiment, decryption can be performed by, for example... Figure 2B The decryption entity 204b mentioned herein performs the actions, but the exemplary embodiments are not limited thereto. In at least one example embodiment, decryption may include obtaining the UE's public key from a desired and / or predetermined location. Upon obtaining the UE's public key, the decryption entity 202b may generate a shared key based on the obtained UE's public key and the decryption entity's private key (e.g., stored within the decryption entity). Furthermore, the decryption entity 202b may use KDF to generate a symmetric key based on the shared key, but is not limited thereto. Continuing on, the decryption entity 202b may decrypt at least partially encrypted partial core dumps based on the generated symmetric key and a decryption algorithm, but the exemplary embodiments are not limited thereto.

[0114] In addition, decryption entity 202b can write a partially decrypted core dump to the output file. Then it checks if it is the last part; if it is, it proceeds to operation 314b, and the process can terminate.

[0115] Figure 4 A flowchart 400 illustrates an operation method for reconstructing a complete core dump according to at least one example embodiment of the concept of the present invention.

[0116] In operation 402, the method includes receiving a trigger (e.g., instruction, signal, etc.) for generating a complete core dump.

[0117] In operation 404, the method includes obtaining RO data from a desired and / or pre-defined file.

[0118] In operation 406, the method includes writing RO data to an output file.

[0119] In operation 408, this method includes retrieving RW data from a partial core dump.

[0120] In operation 410, the method includes writing RW data to an output file to reconstruct a complete core dump.

[0121] Figure 5 A graphical representation 500 depicting the entropy of a typical core dump according to at least one example embodiment of the concept of the present invention is shown. In at least one example embodiment, the entropy of encrypted data (e.g., ≈1) is higher than the entropy of ordinary data present in a RAM core dump. In at least one example embodiment, the entropy representing the offset of assembly instructions (e.g., about 10MB to about 40MB, etc.) in the graphical representation 500 is ≈0.85, but the example embodiment is not limited thereto.

[0122] Figure 6 A graphical representation 600 depicting a core dump with fully entropy encryption according to at least one exemplary embodiment of the present invention is shown. In at least one exemplary embodiment, the entropy of the fully encrypted RAM dump is, for example, ≈1. Furthermore, the encrypted portion of the RAM dump may also include an entropy of, for example, ≈1. In at least one exemplary embodiment, for example, entropy = 1 can be used to detect infringement by detecting the presence of encrypted code regions / other regions, but the exemplary embodiment is not limited thereto.

[0123] While specific language has been used to describe various exemplary embodiments of the inventive concept, no limitation is intended as a result. As will be apparent to those skilled in the art, various working modifications can be made to the method to achieve the inventive concept as taught herein. The accompanying drawings and the foregoing description discuss various exemplary embodiments of the inventive concept. Those skilled in the art will understand that the described elements can be well combined into a single functional element. Alternatively, a particular element can be split into multiple functional elements. For example, an element from one exemplary embodiment can be added to another exemplary embodiment, etc. It is apparent that various exemplary embodiments of the inventive concept can be implemented and practiced differently in other ways within the scope of the appended claims.

Claims

1. A method for generating a core dump in a UE, wherein the UE is a user equipment, the method comprising: Using at least one processor, a trigger is detected, the trigger including instructions for generating a core dump in the UE; Using the at least one processor, the data stored in the memory of the UE is classified into RW data or RO data, where RW stands for Read-Write and RO stands for Read-Only. as well as Using the at least one processor, a partial core dump is generated based on the RW data in the memory. The method further includes: Using the at least one processor, the RO data is segmented into multiple RO data fragments; Using the at least one processor, multiple checksums are generated based on the multiple RO data fragments; and The plurality of checksums are stored in a storage device using the at least one processor.

2. The method according to claim 1, further comprising: Using the at least one processor, a checksum is generated based on the RO data; as well as The at least one processor is used to store the checksum in the storage device.

3. The method according to claim 1, further comprising: Using the at least one processor, in response to the start of the core dump generation, each of the generated checksums is verified based on a plurality of previous checksums stored in the storage device; as well as Using the at least one processor, one or more RO data fragments corresponding to the checksums that failed the verification are appended to the partial core dump.

4. The method of claim 3, further comprising: Using the at least one processor, the one or more RO data fragments are appended to the partial core dump in a random order.

5. The method according to claim 3, further comprising: Using the at least one processor, the one or more RO data fragments are encrypted using the desired cryptographic technique.

6. The method of claim 5, further comprising: Using the at least one processor, one or more encrypted RO data fragments are appended to the partial core dump in a random order.

7. The method according to claim 1, further comprising: Using the at least one processor, determine whether one or more security standards are set in the UE; as well as Using the at least one processor, based on the determined result, at least a portion of the RW data in the partial core dump is encrypted to obtain at least one partially encrypted partial core dump.

8. The method according to claim 7, wherein, The one or more security criteria include at least one of the following: Active remote access tool information, the active remote access tool information being used to selectively encrypt at least a portion of the RW data in the RW data associated with the active remote access tool; Information received from one or more internal security modules for determining, based on a higher risk assessment, at least a portion of the RW data to be encrypted, wherein the one or more internal security modules include at least one of a fake base station detection module, a stack corruption detection module, and a buffer overflow detection module; Information received from one or more external devices indicating the size of at least a portion of the RW data to be encrypted, wherein the one or more external devices include at least one of an application processor and a coprocessor; Specify a fixed range of memory addresses to be encrypted; or Any combination of them.

9. The method according to claim 7, further comprising: Using the at least one processor, a random private key for the UE is generated using cryptographic key exchange technology; Using the at least one processor, the public key of the UE is generated based on the generated random private key and at least one asymmetric cryptographic algorithm; Using the at least one processor, a shared key is generated based on the random private key of the UE and the public key of the decryption device; Using the at least one processor, a symmetric key is generated based on the shared key using a desired key derivation function; Using the at least one processor, the at least one portion of the RW data is encrypted using the symmetric key and the desired encryption algorithm to obtain a partially encrypted core dump of the at least one portion; as well as Using the at least one processor, the public key of the UE is appended to the desired location in the at least one partially encrypted partial core dump.

10. The method of claim 9, further comprising: Using the at least one processor, determine whether a fault occurs during the encryption of at least a portion of the RW data using the symmetric key; as well as Using the at least one processor, based on the determined result, an alternative symmetric key is generated using the key derivation function, the current system time, and the RO region checksum.

11. The method according to claim 10, wherein, The alternative symmetric key is generated in response to a system crash prior to the error-correcting code operation.

12. The method according to claim 10, wherein, The alternative symmetric key is generated in response to a system crash during error-correcting code operation.

13. A method for reconstructing a complete core dump, the method comprising: Using at least one processor, a trigger is received, the trigger including instructions for generating a complete core dump of the UE, i.e., the user equipment; Using the at least one processor, RO data is obtained from a desired partial core dump file, the desired partial core dump file being at least partially encrypted, the RO being read-only; Using the at least one processor, the RO data is written to an output file; Using the at least one processor, RW data is obtained from the desired partial core dump file, where RW refers to read and write operations. as well as Using the at least one processor, the RW data is written to the output file to reconstruct the complete core dump.

14. The method of claim 13, further comprising: Using the at least one processor, identify one or more encrypted portions included in the desired partial core dump file, wherein the one or more encrypted portions include at least one of RO data fragments and encrypted RW data fragments; Using the at least one processor, the identified one or more encrypted portions are decrypted to generate one or more decrypted portions; and Using the at least one processor, the one or more decrypted portions are written to the output file.

15. The method of claim 14, wherein The one or more encrypted portions further include one or more corrupted RO data fragments, and the method further includes: Using the at least one processor, sorting information is obtained from a desired location in the desired partial core dump file, the sorting information corresponding to the original order of the RO data; Using the at least one processor, the one or more damaged RO data segments are reordered based on the sorting information; as well as Using the at least one processor, the one or more corrupted RO data segments are decrypted based on the reordering.

16. The method of claim 15, further comprising: Using the at least one processor, obtain the public key associated with the UE from the desired location in the desired partial core dump file; Using the at least one processor, a shared key is generated based on the obtained public key and the private key stored on the decryption device; Using the at least one processor, a symmetric key is generated based on the shared key using a desired key derivation function; as well as Using the at least one processor, the partially encrypted core dump file is decrypted based on the generated symmetric key and the desired decryption algorithm.

17. A system for generating a core dump in a UE, wherein the UE is a user equipment, the system comprising: At least one processor, the at least one processor being configured to execute computer-readable instructions to perform the following operations: A detection trigger is made, the trigger including instructions for generating a core dump in the UE; The data stored in the memory of the UE is classified into RW data and RO data, which are both in the memory of the UE. RW refers to read-write, and RO refers to read-only. as well as A partial core dump is generated based on the RW data in the memory of the UE. The at least one processor is further configured to: The RO data is segmented into multiple RO data fragments; Generate multiple checksums corresponding to the multiple RO data segments; and The multiple checksums are stored in a storage device.

18. The system according to claim 17, wherein, The at least one processor is further configured to: Generate a checksum based on the RO data; and The checksum is stored in the storage device of the system.

Citation Information

Patent Citations

  • Core dump privacy during application failure

    US20090172409A1

  • Computer and dumping control method

    US20150046754A1