IP Library › Granted Patent US 12,380,218
Granted Patent B2
US 12,380,218 · App. 17/966,702 · Granted Aug 5, 2025

Systems and methods for inspecting browser security vulnerabilities

Inventors: Ian Cohen (Redwood City, CA); Jeremy Barnett (Redwood City, CA); Peter Joles (Redwood City, CA)
G06F21/577G06F21/6245G06F21/645H04L63/1433H04L63/1483G06F2221/034
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,380,218
App. No.
17/966,702
Granted
Aug 5, 2025
Kind
B2
Abstract

Systems and methods are provided for inspecting, identifying, blocking, and combatting browser security vulnerabilities. In various embodiments, an inspection module may execute on a browser accessing a web domain on a first computing device. Inspection modules may dynamically analyze a set of scripts associated with the web domain to identify privacy vulnerabilities. Such vulnerabilities may be blocked and/or combatted to prevent communications of private information to one or more third-, fourth-, . . . , nth-party sites and applications. Embodiments may generate a customized privacy plan directed to one or more privacy vulnerabilities and execute on a graphical user interface on a computing device.

Claims (68)

1. A method for analyzing browser security vulnerabilities, comprising:

receiving information indicative of a request to access a web domain via a browser executing on a first computing device;

analyzing scripts associated with the web domain to identify a privacy vulnerability; and

generating a customized privacy determination based on the privacy vulnerability,

wherein analyzing the scripts associated with the web domain comprises;

determining a set of information associated with a risk type;

identifying a browser operation utilizing the set of information; and

assessing a risk level associated with the privacy vulnerability based on the browser operation, wherein the risk level indicates a priority level for addressing the privacy vulnerability; and

wherein the risk type comprises at least one of malware, personal identifiable information, session replay, fingerprinting, trackers, young domains, a cookie request, a phishing attempt, a URL redirection, a bad secure sockets layer (SSL).

2. The method of claim 1 , wherein the set of information comprises identifying information about one or more of a user, an interaction on the web domain, or a computing device associated with the user.

3. The method of claim 1 , wherein the browser operation includes at least one of sending or receiving the set of information to an external party.

4. The method of claim 1 , wherein generating the customized privacy determination occurs prior to accessing the web domain.

5. A method for analyzing browser security vulnerabilities, comprising:

receiving information indicative of a web domain access request via a browser executing on a first computing device;

analyzing scripts associated with the web domain to identify a risk level associated with a privacy vulnerability, wherein the risk level indicates a priority level for addressing the privacy vulnerability;

generating a customized privacy determination based on the privacy vulnerability; and,

wherein analyzing scrips occurs asynchronously with an access of the web domain.

6. A system for analyzing browser security vulnerabilities comprising:

an inspection module operating on a computing device configured to access a web domain via a browser, wherein the inspection module comprises instructions, which when executed on a processor associated with the computing device, cause the processor to at least:

receive information indicative of a web domain access request via a browser executing on a first computing device;

analyze scripts associated with the web domain to identify a risk level associated with a privacy vulnerability, wherein the risk level indicates a priority level for addressing the privacy vulnerability;

generate a customized privacy determination based on the privacy vulnerability; and

wherein the privacy vulnerability is based on a customized, configurable set of privacy considerations received at a user interface associated with the computing device.

7. The system of claim 6 , wherein the instructions to analyze scripts associated with the web domain further comprise:

determining a set of information associated with a risk type;

identifying a browser operation utilizing the set of information; and

assessing a risk level based on the browser operation.

8. The system of claim 7 , wherein the risk type comprises at least one of: malware, personally identifiable information, session replay, fingerprinting, trackers, young domains, a cookie request, a phishing attempt, a URL redirection, a bad secure sockets layer (SSL), and wherein the set of information comprises identifying information about one or more of a user, an interaction on the web domain, or a computing device associated with the user.

9. The system of claim 6 , wherein the browser operation includes at least one of sending or receiving the set of information to an external party.

10. A system for analyzing browser security vulnerabilities comprising:

an inspection module operating on a computing device configured to access a web domain via a browser, wherein the inspection module comprises instructions, which when executed on a processor associated with the computing device, cause the processor to at least:

receive information indicative of a web domain access request via a browser executing on a first computing device;

analyze scripts associated with the web domain to identify a risk level associated with a privacy vulnerability, wherein the risk level indicates a priority level for addressing the privacy vulnerability;

generate a customized privacy determination based on the privacy vulnerability; and,

instructions that cause the processor to block a transfer of information associated with the privacy vulnerability.

11. A system for analyzing browser security vulnerabilities comprising:

an inspection module operating on a computing device configured to access a web domain via a browser, wherein the inspection module comprises instructions, which when executed on a processor associated with the computing device, cause the processor to at least:

receive information indicative of a web domain access request via a browser executing on a first computing device;

analyze scripts associated with the web domain to identify a risk level associated with a privacy vulnerability, wherein the risk level indicates a priority level for addressing the privacy vulnerability;

generate a customized privacy determination based on the privacy vulnerability; and,

display the customized privacy determination on a user interface.

12. A non-transitory, computer-readable medium comprising instructions that, when executed on a computing device, cause the computing device to:

receive information indicative of a web domain access request via a browser;

analyze scripts associated with the web domain to identify a risk level associated with a privacy vulnerability, wherein the risk level indicates a priority level for addressing the privacy vulnerability;

generate a customized privacy determination based on the privacy vulnerability; and,

blocking a transfer of information associated with the privacy vulnerability.

13. A non-transitory, computer-readable medium comprising instructions that, when executed on a computing device, cause the computing device to:

receive information indicative of a web domain access request via a browser;

analyze scripts associated with the web domain to identify a risk level associated with a privacy vulnerability, wherein the risk level indicates a priority level for addressing the privacy vulnerability; and

generate a customized privacy determination based on the privacy vulnerability; and disable a transfer of referrer information.

14. A non-transitory, computer-readable medium comprising instructions that, when executed on a computing device, cause the computing device to:

receive information indicative of a web domain access request via a browser;

analyze scripts associated with the web domain to identify a risk level associated with a privacy vulnerability, wherein the risk level indicates a priority level for addressing the privacy vulnerability;

generate a customized privacy determination based on the privacy vulnerability; and

block a transfer of information associated with the privacy vulnerability before an interaction with the web domain by a user.

15. A non-transitory, computer-readable medium comprising instructions that, when executed on a computing device, cause the computing device to:

receive information indicative of a web domain access request via a browser;

analyze scripts associated with the web domain to identify a privacy vulnerability;

generate a customized privacy determination based on the privacy vulnerability; and

send spoofed information to a requesting party associated with the privacy vulnerability.

16. A non-transitory, computer-readable medium comprising instructions that, when executed on a computing device, cause the computing device to:

receive information indicative of a request to access a web domain request via a browser;

analyze scripts associated with the web domain to identify a privacy vulnerability;

generate a customized privacy determination based on the privacy vulnerability; and,

wherein analyzing the scripts associated with the web domain comprises;

determining a set of information associated with a risk type;

identifying a browser operation unitizing the set of information; and

assessing a risk level associated with the privacy vulnerability based on the browser operation, wherein the risk level indicates a priority level for addressing the privacy vulnerability; and wherein risk type comprises at least one of: malware, personal identifiable information, session replay, fingerprinting, trackers, young domains, a cookie request, a phishing attempt, a URL redirection, a bad secure sockets layer (SSL), and wherein the set of information comprises identifying information about one or more of a user, an interaction on the web domain, or a computing device associated with the user.

Continuity (2)
Provisional Application 63393796 · Jul 29, 2022
Related Publication 20240039947A1 · Feb 1, 2024
References Cited (46)
US 8079080B2 · Borders · 2011 [cited by examiner]
US 8752183B1 · Heiderich · 2014 [cited by examiner]
US 8752208B2 · Shulman · 2014 [cited by examiner]
US 8832834B2 · Lee · 2014 [cited by examiner]
US 8949990B1 · Hsieh · 2015 [cited by examiner]
US 9038184B1 · Mann · 2015 [cited by examiner]
US 9178904B1 · Gangadharan · 2015 [cited by examiner]
US 9392003B2 · Amsler · 2016 [cited by examiner]
US 9686288B2 · Kikuchi · 2017 [cited by examiner]
US 9906553B1 · Ainslie · 2018 [cited by examiner]
US 10108817B2 · Riva · 2018 [cited by examiner]
US 10681063B1 · Silva · 2020 [cited by examiner]
US 11777992B1 · Cross · 2023 [cited by examiner]
US 20070107057A1 · Chander · 2007 [cited by examiner]
US 20070136579A1 · Levy · 2007 [cited by examiner]
US 20090132481A1 · Toub · 2009 [cited by examiner]
US 20100037317A1 · Oh · 2010 [cited by examiner]
US 20100125913A1 · Davenport · 2010 [cited by examiner]
US 20110289582A1 · Kejriwal · 2011 [cited by examiner]
US 20140173744A1 · Borohovski · 2014 [cited by examiner]
US 20150074390A1 · Stoback · 2015 [cited by examiner]
US 20160323309A1 · Sethi · 2016 [cited by examiner]
US 20180018465A1 · Carey · 2018 [cited by examiner]
US 20180218145A1 · Hussain · 2018 [cited by examiner]
US 20190108353A1 · Sadeh · 2019 [cited by examiner]
US 20190132355A1 · Egbert · 2019 [cited by examiner]
US 20210012021A1 · Pickhardt · 2021 [cited by examiner]
US 20220272127A1 · Yawalkar · 2022 [cited by examiner]
US 20230038796A1 · Bhatkar · 2023 [cited by examiner]
US 20230039079A1 · Philip · 2023 [cited by examiner]
US 20230403300A1 · Narayan · 2023 [cited by examiner]
US 20240354151A1 · Argov · 2024 [cited by examiner]
US 20240378267A1 · Argov · 2024 [cited by examiner]
US 20240394412A1 · Shin · 2024 [cited by examiner]
WO WO2008016915A2 · 2008 [cited by examiner]
WO WO2011094312A1 · 2011 [cited by examiner]
Toreini et al.; “DOMtegrity: ensuring web page integrity against malicious browser extensions”, 2019, Springer, International Journal of Information Security, pp. 801-814. (Year: 2019). [cited by examiner]
Pawade et al.; “Implementation of Extension for Browser to Detect Vulnerable Elements on Web Pages and Avoid Clickjacking”, 2016, IEEE, pp. 226-230. (Year: 2016). [cited by examiner]
Hamed et al.; “Privacy Risk Assessment for Web Tracking”, 2016, IEEE, Canadian Conference on Electrical and Computer Engineering (CCECE), pp. 1-6. (Year: 2016). [cited by examiner]
Acker et al.; “Monkey-in-the-browser: Malware and Vulnerabilities in Augmented Browsing Script Markets”, 2014, ACM, pp. 525-530. (Year: 2014). [cited by examiner]
Barua et al.; “Protecting Web Browser Extensions from JavaScript Injection Attacks”, 2013, International Conference on Engineering of Complex Computer Systems, pp. 188-197. (Year: 2013). [cited by examiner]
Rehman et al.; “On Detection and Prevention of Clickjacking Attack for OSNs”, 2013 11th International Conference on Frontiers of Information Technology, pp. 160-165. (Year: 2013). [cited by examiner]
Dhawan et al.; “Analyzing Information Flow in JavaScript-based Browser Extensions”, 2009 Annual Computer Security Applications Conference, pp. 382-391. (Year: 2009). [cited by examiner]
Kerschbaumer et al.; “Hardening Firefox against Injection Attacks”, 2020, IEEE, pp. 653-663. (Year: 2020). [cited by examiner]
Barua et al.; “Protecting Web Browser Extensions from JavaScript Injection Attacks”, 2013, IEEE, pp. 188-197. (Year: 2013). [cited by examiner]
Dhawan et al.; “Analyzing Information Flow in JavaScript-based Browser Extensions”, 2009, IEEE, pp. 382-391. (Year: 2009). [cited by examiner]