search

Aurore54F / DoubleX

Statically Detecting Vulnerable Data Flows in Browser Extensions at Scale
GNU Affero General Public License v3.0
63 stars 11 forks source link

Timing information #3

Closed Luca-Pistor closed 2 years ago

Luca-Pistor commented 2 years ago

Currently, running a DoubleX program will not print information to stdout until it finishes processing an extension, or an error occurs. This may make it difficult to determine how much time is left in various processing phases, which would be useful for processing large extensions.

Aurore54F commented 2 years ago

Thanks. Added info and benchmark for the following steps (note elements 1-4 refer to the content script (cs) and 5-8 to the background page (bp); WA later refers to a Web Application):

CURRENT STATE Successfully got Esprima AST in XXXs CURRENT STATE Successfully produced the AST in XXXs CURRENT STATE Successfully produced the CFG in XXXs CURRENT STATE Successfully produced the PDG in XXXs CURRENT STATE Successfully got Esprima AST in XXXs CURRENT STATE Successfully produced the AST in XXXs CURRENT STATE Successfully produced the CFG in XXXs CURRENT STATE Successfully produced the PDG in XXXs CURRENT STATE Successfully collected all messages exchanged in XXXs CURRENT STATE Successfully linked the messages sent and received in XXXs CURRENT STATE Successfully collected the dangers and elements from the WA in the cs in XXXs CURRENT STATE Successfully collected the dangers and elements from the WA in the bp in XXXs CURRENT STATE Successfully analyzed and collected the vulnerabilities in the cs in XXXs CURRENT STATE Successfully analyzed and collected the vulnerabilities in the bp in XXXs