Browser Version Verification via Exception Throwing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer security systems fail to effectively detect fraudulent and malicious activities by not leveraging inconsistencies between self-reported and actual browser information, allowing malicious entities to exploit older browser versions for account takeover and unauthorized transactions.
Innovation Solution
Implementing a program, such as JavaScript, on user devices to throw exceptions specific to certain browser versions, allowing servers to analyze inconsistencies between reported and actual browser versions, and optionally performing CAPTCHA tests to verify human user identity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing fraud detection systems rely on self-reported browser information, then the system is simple to operate, but the system cannot detect malicious activities that exploit browser version inconsistencies
Solution Approach 1:
The system performs preliminary actions by executing version-specific code within the browser before evaluating fraud risk. This code is designed to throw exceptions in older browser versions, allowing the system to proactively detect browser version inconsistencies before malicious activities can proceed. The preliminary execution of version-discriminating code enables the system to identify suspicious browsers that claim to be newer versions but exhibit behavior characteristic of older versions.
Solution Approach 2:
The patent introduces an intermediary mechanism - version-discriminating code executed within the browser - that acts as a mediator between the self-reported browser version and the actual browser capabilities. This intermediary code throws exceptions in specific browser versions, providing the fraud detection system with indirect evidence of the true browser version without requiring direct access to browser internals. The intermediary exception-throwing code bridges the gap between reported and actual browser identities.
2Reliability
If the system executes version-discriminating code to detect browser inconsistencies, then fraud detection accuracy improves, but the processing time and computational resources increase
Solution Approach 1:
The system applies partial action by executing only specific version-discriminating code snippets rather than comprehensive browser analysis. The implemented code throws exceptions in particular browser versions (e.g., older versions with known vulnerabilities) rather than attempting to verify all possible browser configurations. This selective approach to version discrimination reduces processing overhead while maintaining effective detection of the most common fraudulent browser version scenarios.
3Reliability
If the system flags requests with elevated risk levels based on browser inconsistencies, then account security improves, but user convenience deteriorates due to additional verification steps
Solution Approach 1:
The system applies local quality by implementing differential verification based on detected browser characteristics. Rather than uniformly applying additional security steps to all users, the system selectively flags only those requests exhibiting browser version inconsistencies for elevated risk evaluation. Legitimate users with consistent browser information experience normal access flow, while suspicious requests trigger additional verification such as CAPTCHA challenges. This localized application of security measures maintains user convenience for legitimate operations while providing enhanced protection for potentially fraudulent attempts.
Data Source
AI summary
A request to access one or more server resources is received from a user device. Based on the request, a purported version of a browser running on the user device is determined. The user device executes a program within the browser, according to various embodiments, which throws one or more exceptions associated with one or more particular browser versions. The results of the exceptions may be analyzed to determine whether the purported version of the browser appears to be a true version of the browser. If the analysis indicates that the purported version of the browser is not accurate, the request to access the one or more server resources may be evaluated at an elevated risk level. Inaccurately reported browser versions may indicate an attempt to gain unauthorized access to an account, and thus, being able to detect a falsely reported browser version can help improve computer security.