OWASP Orizon Project XML

From OWASP
Revision as of 14:51, 12 November 2008 by Thesp0nge (Talk | contribs)

Jump to: navigation, search

Contents

The Orizon check XML schema

Security checks can be divided in:

  • design_check
  • keyword_check
  • execution_check
  • stats_check

Statistics check

<stats
    subj=[loc | loC]
    verb=[lt | gt | le | ge | ne | eq | ratio]
    [ direct_object= [loc | loC] ]
    [modifier = "percentage"]
    value=numeric value
  />

where:

  • Subject can be one of the following:
    • loc: line of code
    • loC: line of Comment
  • verb is the boolean comparison operator between the subject and the value:
    • lt: lesser than
    • gt: grater than
    • le: lesser or equal than
    • ge: greater or equal than
    • ne: not equal than
    • eq: equal than
    • ratio: indicates the ratio subj versus direct_object

Design check

Design checks are about source file design (how many class are contained in a source? how many methods? what is the scope of the method A?).


  <design 
    subj=[class|field|attribute]
    name=the subject name when appliable
    verb=[count|has_scope]
    value=the value being checked
  />

When intended as String, the value argument can be a "|" separated list of strings ("public|private").

  <design 
    subj="class"
    verb=[extends|implements]
    value=the value being checked
  />

To check if a class contains a specific method (e.g. to check if that class can be serialized or not), this notation must be used.

  <design 
    subj="class"
    verb="contains"
    value="method"
  >
    <what name="the method name" type="the method return type" modifier="a | separated list of modifier attributes" />
  &lt/design>
 

keyword_check, about keyword specific checks

  <keyword
    name=keyword name
  />

execution_check: extra care must be taken for parameter in this desing...

  <exec
    caller_class=a class name
    caller_method=a method name
  />

The Orizon Input file XML schema

Orizon 1.0 will bring 3 new subsystems in Jericho engine:

  • local analisys (control flow graph)
  • global analisys (call graph)
  • taint propagation analisys (data graph)

Each of this subsystems will use a different input file provided by the translator, so each source file will be translated in 3 different XML files with different schema of course.

Local analisys

Global analisys

Taint propagation analisys

This subsystem is devoted to analyze variable content and how data is managed by the application.

Here is the schema to be used to describe a generic operation over a variable or a socket or a generic I/O operation.

 <taint
      subj="[variable|socket|sql|file]"
      name="the variable name"
      type="the variable data type"
      verb="[created|modified|deleted|read_data|write_data]"
      constant="[yes|no]"
      must_reduce="[yes|no]"
      value"the value being used to fill the variable"
 >
      expression to be reduced...
 </taint>

Here there are some example to understand better how instructions over variable, will be translated to XML.

    • Variable declaration

To better describe variable declaration we must discriminate from simple variable rather than complex objects in OO programming languages.

If we need to declare a brand new integer value,

  int a;

we will obtain

  <taint subj="variable" name="a" type="int" verb="created" constant="" value="" must_reduce="no" />

If we choose to create a new variable with a init value,

  int b = 3;

we will obtain

  <taint subj="variable" name="b" type="int" verb="created" constant="" value="3" must_reduce="no" />

Now lets create an object rather than a simple variable.

  String c = new String("A new string");

The correspondent XML will be

  <taint subj="variable" name="c" type="String" verb="created" constant="" value="A new string" must_reduce="no" />

What happens if some complex constructor call is issued

  String d = new String((new Integer(3)).toString());

This example is quite odd, but it's a common practice to have very complex object constructor calls.

  <taint subj="variable" name="d" type="String" verb="created" constant="" value="" must_reduce="yes">
      <taint subj="variable" name="dyno1" type="Integer" verb="created" value="3" must_reduce="no">
      <call variable="dyno1" method="toString()">
            <result type="String">3</result>
      </call>  
  </taint>
    • Generic non constant assignment

Let a be an integer variable. We want to stuff volatile value of '5' into it...

  a = 5;

it becomes

  <taint subj="variable" name="a" verb="modified" constant="no" value="5" />