4MMSR-Network Security-2012-2013-taint assisted dom xss fuzzing : Différence entre versions

De Ensiwiki
Aller à : navigation, rechercher
Ligne 11 : Ligne 11 :
 
|keywords=fuzzing,DOM/type-0 XSS,data tainting
 
|keywords=fuzzing,DOM/type-0 XSS,data tainting
  
|description=DOM XSS is an injection vulnerability for which few attack grammars do exist. The problem formalization can be derived from .  
+
|description=DOM XSS is an injection vulnerability for which few attack grammars do exist. The problem formalization can be derived from [http://car-online.fr/en/spaces/fabien_duchene/publications/2012-04-SecTest-ICST/]. There exist a fuzzer integrated in the penetration testing tool Dominator Pro [https://dominator.mindedsecurity.com/]. It is not clear how this module does perform: it is likely that this module iteratively submits all values from a dictionary and keeps iterating until a given test verdict is obtained. In this mini research exercise we want to address this fuzzing process in two ways:
 +
* how to generate an input sequence knowing previously submitted sequences?
 +
* how to assess if a given input sequence is promising towards triggering this bug?
  
 
|expected_output=
 
|expected_output=
 +
 
* formalize the DOM XSS problem
 
* formalize the DOM XSS problem
 
* write a DOM-XSS attack grammar
 
* write a DOM-XSS attack grammar

Version du 31 décembre 2012 à 12:23

Mycomputer.png  Deuxième Année  CDROM.png  Informatique  Security logo.png  Sécurité  4MMSR-mini research logo.jpg  4MMSR-mini research project 

Taint Assisted DOM-XSS Fuzzing

This is a "mini" research project for the course 4MMSR-Network Security

Keywords

fuzzing,DOM/type-0 XSS,data tainting

Description

DOM XSS is an injection vulnerability for which few attack grammars do exist. The problem formalization can be derived from [1]. There exist a fuzzer integrated in the penetration testing tool Dominator Pro [2]. It is not clear how this module does perform: it is likely that this module iteratively submits all values from a dictionary and keeps iterating until a given test verdict is obtained. In this mini research exercise we want to address this fuzzing process in two ways:

  • how to generate an input sequence knowing previously submitted sequences?
  • how to assess if a given input sequence is promising towards triggering this bug?

Expected output

  • formalize the DOM XSS problem
  • write a DOM-XSS attack grammar
  • interface with Dominator Pro to obtain:
    • the number of tainted nodes
    • if a DOM XSS attack did occur or not (test verdict)
  • write a fitness function for directing DOM XSS fuzzing
  • write an evolutionary fuzzer

Research Questions

  • propose a methodology for producing a DOM-XSS grammar
  • what are the intuitions for writing the most relevant fitness function dimensions?
  • compare the built-in DOMinator Pro fuzzer with the one you wrote (criteria to be defined)

References

Tools

Results

{{{results}}}

Get Started!

  • create an archive on the ensimag server, so that only your team members and I have access to it.
  • Créer_une_archive_partagée_avec_Git
  • obviously, do not forget to send me the path afterwards

Contacts

Fabien Duchene