Web Browser URL Masking for Token Leakage Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The leakage of security tokens in URLs poses a risk to privacy and security, particularly when previewing web pages, as tokens can be exposed in log files or referrer fields, with no known solution for script tags.

Innovation Solution

Incorporating a JavaScript snippet in the HTML header to manipulate the URL, using the browser's history API to change the URL temporarily to a sacrificial URL, preventing token exposure in referrer fields, and then restoring the original URL.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the actual URL with access token is displayed in the browser address bar and used in HTTP requests, then users can see the correct URL and resources can be loaded properly, but security tokens are exposed in referrer fields and log files

Engineering Contradiction:
ImproveURL correctnessVSAvoidtoken exposure
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a sacrificial URL as an intermediary that temporarily replaces the actual URL in the browser address bar during resource loading. This sacrificial URL does not contain the access token, so when it appears in referrer fields and log files, the token remains protected. After resource loading completes, the original URL is restored. This mediator approach allows the system to display a safe URL during vulnerable operations while maintaining the functionality of the actual URL.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If a sacrificial URL is used in the browser address bar during resource loading, then security tokens are protected from leakage in referrer fields, but the URL displayed to users is incorrect

Engineering Contradiction:
Improvetoken protectionVSAvoidURL accuracy
Core Design Contradiction:
Object-affected harmful factorsVSLoss of information

Solution Approach 1:

The patent implements a dynamic URL switching mechanism where the browser address bar URL changes based on the operation phase. During resource loading, the URL dynamically switches to the sacrificial version without the access token to prevent exposure. After loading completes, the URL dynamically reverts to the actual URL with the access token. This temporal separation ensures token protection during vulnerable operations while maintaining URL accuracy for user navigation.

Inventive Principle:
Principle #15Dynamics

3Object-affected harmful factors

If the URL is manipulated to hide the access token, then privacy and security are enhanced, but the URL functionality may be compromised

Engineering Contradiction:
Improveprivacy protectionVSAvoidURL functionality
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent performs preliminary URL manipulation by switching to the sacrificial URL before resource loading begins. This preliminary action ensures that no referrer information containing the access token is exposed during the loading process. The original URL is preserved and restored after loading completes, ensuring that URL functionality remains intact for subsequent operations. This timing-based approach protects privacy during the vulnerable loading phase while maintaining full functionality afterward.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9680834B2Web document preview privacy and security protection
Publication Date: 2017.06.13 ADOBE INC
  • US9680834B2 patent drawing
  • US9680834B2 patent drawing
  • US9680834B2 patent drawing

AI summary

Techniques are disclosed for protecting the privacy and security of data associated with a web document. A web browser is configured to manipulate the URL, which contains an access token, of a preview web page document before the browser loads external resources (e.g., web page content) linked from the preview web page document. For example, the browser may change a current page URL containing the access token to another sacrificial URL that does not include the token. In addition, the browser will send the sacrificial URL, rather than the original URL, as a referrer to the various resources that provide the web page content, which prevents exposure of the access token to those resources while the web page content is loading. After the web page content is loaded into the browser, the current page URL of the browser is changed back to the original URL.