# US 2022/0035911 A1 · Active signaling in response to attacks on a transformed binary

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0035911 A1
- Document ID: US20220035911A1
- Status: Published application
- Kind: A1
- Application number: 17/389,195
- Filed: 2021-07-29
- Published: 2022-02-03
- Earliest claimed: 2020-07-31
- Assignees: Runsafe Security, Inc.
- Applicants: Runsafe Security, Inc.
- Inventors: Shane FRY; Brent BESSEMER
- Web page: https://patentgrep.com/patent/US20220035911A1

## CPC

- G06F 21/554: {involving event detection and direct action}
- G06F 21/54: by adding security routines or objects to programs
- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An apparatus and method for responding to an invalid state occurrence encountered during execution of a third-party application program is included. The apparatus performing the method which includes registering a trap signal handler with a kernel of an operating system. The method also including intercepting calls from the third-party application program to the operating system and processing an exception signal corresponding to the invalid state to generate a response. The response including performing a signal reporting process.

## Claims

### Claim 1

A method for responding to an invalid state occurrence encountered during execution of a third-party application program, comprising:
registering a trap signal handler with a kernel of an operating system;
intercepting calls from the third-party application program to the operating system;
processing an exception signal corresponding to the invalid state to generate a response, the response including performing a signal reporting process.

### Claim 2 (depends on 1)

The method of claim 1, wherein the signal reporting process includes logging and/or reporting to a security incident and event management (SEIM) tool information associated with the invalid state.

### Claim 3 (depends on 2)

The method of claim 2, wherein the information associated with the invalid state includes a processor register state at a time when the exception signal was generated, stack backtraces, a type of the exception signal, and/or if the third-party application program is a transformed binary, information about the transformed binary.

### Claim 4 (depends on 1)

The method of claim 1, wherein the signal reporting process includes utilizing an interrupt handler in the kernel to override or modify the behavior of an exception handler module in the kernel.

### Claim 5 (depends on 1)

The method of claim 1, wherein the signal reporting process includes determining whether there is evidence to support if the invalid state corresponds to a cyber attack or a non-threatening event.

### Claim 6 (depends on 1)

The method of claim 1, wherein the processing the exception signal corresponding to the invalid state includes:
receiving the exception signal from an exception handler module of the kernel; and
collecting exception information on the exception signal,
wherein the signal reporting process includes the collected exception information.

### Claim 7 (depends on 6)

The method of claim 6, wherein the processing the exception signal corresponding to the invalid state further includes:
determining whether a user signal handler is registered with the trap signal handler,
wherein, if the user signal handler is registered with the trap signal handler, the exception signal is returned to the user signal handler in the third-party application program, and
wherein, if the user signal handler is not registered with the trap signal handler, execution of the third-party application program is aborted.

### Claim 8 (depends on 1)

The method of claim 1, wherein the registering the trap signal handler with the kernel includes:
receiving call parameters via an entry point in an initialize shim procedure;
loading a system flag with a defined constant, the system flag associated with a signal of interest for the invalid state;
loading an address of a trap signal handler into memory;
registering with a system call module in the kernel the address of the trap signal handler and settings of the system flag; and
receiving a return value from the system call module.

### Claim 9 (depends on 1)

The method of claim 1, wherein the invalid state corresponds to memory corruption.

### Claim 10 (depends on 1)

The method of claim 1, wherein the intercepting calls from the third-party application program includes:
receiving a user signal requesting a system call to the kernel to register a user signal handler; and
performing one of trap operation on the system call to allow the trap signal handler to process the user signal or a pass though operation that bypasses the trap signal handler.

### Claim 11

A non-transitory computer-readable storage medium having stored thereon instructions for responding to an invalid state occurrence encountered during execution of a third-party application program which when executed by a processor of an electronic device cause the processor to:
register a trap signal handler with a kernel of an operating system;
intercept calls from the third-party application program to the operating system;
process an exception signal corresponding to the invalid state to generate a response, the response including performing a signal reporting process.

### Claim 12 (depends on 11)

The non-transitory computer-readable storage medium of claim 11, the signal reporting process includes logging and/or reporting to a security incident and event management (SEIM) tool information associated with the invalid state, the invalid state corresponding to a memory corruption.

### Claim 13 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the information associated with the invalid state includes a processor register state at a time when the exception signal was generated, stack backtraces, a type of the exception signal, and/or if the third-party application program is a transformed binary, information about the transformed binary.

### Claim 14 (depends on 11)

The non-transitory computer-readable storage medium of claim 11, wherein the processing the exception signal corresponding to the invalid state includes:
receiving the exception signal from an exception handler module of the kernel; and
collecting exception information on the exception signal,
wherein the signal reporting process includes the collected exception information.

### Claim 15 (depends on 11)

The non-transitory computer-readable storage medium of claim 11, wherein the registering the trap signal handler with the kernel includes:
receiving call parameters via an entry point in an initialize shim procedure;
loading a system flag with a defined constant, the system flag associated with a signal of interest for the invalid state;
loading an address of a trap signal handler into memory;
registering with a system call module in the kernel the address of the trap signal handler and settings of the system flag; and
receiving a return value from the system call module.

### Claim 16

An apparatus for responding to an invalid state occurrence encountered during execution of a third-party application program, comprising:
memory; and
a processor coupled to the memory and configured for:
registering a trap signal handler with a kernel of an operating system;
intercepting calls from the third-party application program to the operating system;
processing an exception signal corresponding to the invalid state to generate a response, the response including performing a signal reporting process.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein the signal reporting process includes logging and/or reporting to a security incident and event management (SEIM) tool information associated with the invalid state, the invalid state corresponding to a memory corruption.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein the information associated with the invalid state includes a processor register state at a time when the exception signal was generated, stack backtraces, a type of the exception signal, and/or if the third-party application program is a transformed binary, information about the transformed binary.

### Claim 19 (depends on 16)

The apparatus of claim 16, wherein the processing the exception signal corresponding to the invalid state includes:
receiving the exception signal from an exception handler module of the kernel; and
collecting exception information on the exception signal,
wherein the signal reporting process includes the collected exception information.

### Claim 20 (depends on 16)

The apparatus of claim 16, wherein the registering the trap signal handler with the kernel includes:
receiving call parameters via an entry point in an initialize shim procedure;
loading a system flag with a defined constant, the system flag associated with a signal of interest for the invalid state;
loading an address of a trap signal handler into memory;
registering with a system call module in the kernel the address of the trap signal handler and settings of the system flag; and
receiving a return value from the system call module.
