Web Interface Injection Detection via Reference Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The injection of unauthorized code into webpages by third-party services poses significant security threats and disrupts user experience, as existing technologies fail to efficiently detect and remove such injected elements without affecting the rendering of content or increasing processing overhead.

Innovation Solution

A processing device compares rendered content interfaces with reference interfaces to identify injected elements, employing detection techniques that analyze characteristics and attributes to neutralize these elements by modifying their parameters, making them invisible or removable without affecting the original content rendering.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If unauthorized code injection detection is implemented, then security is improved, but processing overhead increases

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary comparison of rendered interface elements against expected interface definitions before the injected code can execute its harmful function. By detecting discrepancies between expected and actual interface elements in advance, the system neutralizes potential threats before they can disrupt processing or compromise security, thereby improving security without adding significant processing overhead during critical operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary comparison layer between the content provider and the rendering process. This intermediary mechanism compares rendered interface elements against expected definitions, acting as a mediator that identifies injected elements without requiring direct analysis of potentially malicious code, thus improving security while maintaining efficient processing through indirect verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If injected elements are removed or neutralized, then security is improved, but content rendering may be affected

Engineering Contradiction:
ImprovesecurityVSAvoidcontent rendering
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system applies local quality by selectively neutralizing only the specific injected interface elements that pose security threats, while leaving the rest of the content interface unchanged. By targeting only the harmful discrepancies between expected and actual interface elements, the system maintains security without affecting the overall content rendering and user experience.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system converts the harmful effect of injected elements into a benefit by using the comparison between expected and actual interface elements to identify and neutralize threats. The presence of injected elements, while harmful in itself, provides detectable discrepancies that enable the system to locate and remove them, thereby transforming the security threat into an opportunity for automated detection and protection.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

3Reliability

If third-party services are blocked, then security is improved, but functionality may be lost

Engineering Contradiction:
ImprovesecurityVSAvoidfunctionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system applies partial action by selectively blocking only the specific injected elements that are identified as security threats through interface comparison, rather than implementing a blanket block of all third-party content. This approach allows legitimate third-party functionality to operate normally while neutralizing only the harmful injected elements, thereby maintaining security without sacrificing essential functionality.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10554682B2Detecting and removing injected elements from content interfaces
Publication Date: 2020.02.04 NAMOGOO TECH
  • US10554682B2 patent drawing
  • US10554682B2 patent drawing
  • US10554682B2 patent drawing

AI summary

Systems and methods are disclosed for detecting and removing injected elements from content interfaces. In one implementation, a processing device receives a content interface from a content provider, processes the content interface to identify elements of the interface that may not have been received from the content provider, compares the content interface with corresponding reference interfaces to identify elements of the content interface that are not present in the reference interfaces, processes the identified elements to determine how the identified elements affect a rendering of the content interface on the device, and modifies a rendering of the content interface on the device based on the manner in which the identified elements affect the rendering of the content interface on the device.