Memory Scan for Heap Spray Attack Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer systems are ineffective in detecting and mitigating code injection attacks, particularly heap spray attacks, which exploit heap memory to execute malicious code or cause denial-of-service, posing a significant threat to applications like web browsers and operating systems.

Innovation Solution

A computer system and method that scans memory sections for non-operational instructions, determines the presence of a heap spray attack by analyzing the number and spatial locality of no-ops, and takes defensive actions such as terminating the program or isolating affected sections, utilizing techniques like Hidden Markov Models to detect and mitigate such attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If heap memory is sprayed with no-ops to enable code execution redirection, then code injection capability is improved, but system security deteriorates

Engineering Contradiction:
Improvecode execution capabilityVSAvoidsecurity vulnerability
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary scanning of heap memory sections to detect no-op instructions before they can be executed as part of a code injection attack. By proactively identifying and isolating malicious no-op sequences, the system prevents the attack from succeeding while maintaining legitimate heap functionality.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary detection layer between the heap memory and the CPU execution pipeline. This intermediary scans memory sections for suspicious no-op patterns and can intercept malicious code redirection attempts, allowing legitimate heap operations to proceed while blocking security threats.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If heap memory is sprayed with large volume of no-ops, then denial-of-service effect is achieved, but system availability deteriorates

Engineering Contradiction:
Improvedenial-of-service capabilityVSAvoidsystem availability
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The system scans heap memory sections in advance to detect excessive no-op sequences that could indicate a denial-of-service attack. By identifying these patterns before they consume excessive CPU resources, the system can terminate the malicious process early, preventing the denial-of-service condition from materializing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism that monitors heap memory usage and CPU execution patterns. When the system detects abnormal no-op sequences exceeding threshold values, it triggers corrective actions such as process termination or memory isolation, thereby preventing denial-of-service attacks while maintaining system availability.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If scanning is performed on all memory sections, then detection precision is improved, but processing time increases

Engineering Contradiction:
Improveattack detection accuracyVSAvoidmemory scanning time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies local quality by focusing scanning resources on specific heap memory sections that are most susceptible to code injection attacks, rather than uniformly scanning all memory. This targeted approach maintains high detection precision for critical areas while reducing overall processing time.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs partial scanning of memory sections by analyzing only the portions most likely to contain malicious no-op sequences. By applying threshold-based filtering and scanning only suspicious regions, the system achieves adequate detection precision without the time cost of exhaustive full-memory scanning.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11263307B2Systems and methods for detecting and mitigating code injection attacks
Publication Date: 2022.03.01 DIGITAL IMMUNITY LLC
  • US11263307B2 patent drawing
  • US11263307B2 patent drawing
  • US11263307B2 patent drawing

AI summary

The present disclosure generally relates to computer security and malware protection. In particular, the present disclosure is generally directed towards systems and methods for detecting and mitigating a code injection attack. In one embodiment the systems and methods may detect a code injection attack by scanning identified sections of memory for non-operational machine instructions (“no-ops”), detecting a code injection attack based on the scan(s) and mitigating the code injection attack by taking one or more defensive actions.