The string returned from scan_address in GreyHack places a \n\n after each vulnerability. Greybel does not.
This is significant because the existence of the double newline allows you to easily split the string into a list of separate attacks.
For example, GreyHack produces the following:
decompiling source...
searching unsecure values...
Unsafe check: loop in array objectotalbytebu. Buffer overflow.
* Checking root active user.
* Using namespace kernel_module.so compiled at version >= 1.0.0
Unsafe check: string copy in true. Buffer overflow.
* Checking an active user.
* Using namespace kernel_module.so compiled at version >= 1.0.0
Unsafe check: loop in array s_h. Buffer overflow.
* Checking root active user.
* Using namespace kernel_module.so compiled at version >= 1.0.0
Unsafe check: string copy in gotoa. Buffer overflow.
* Checking registered users equal to 4.
Unsafe check: loop in array headdr. Buffer overflow.
* Using namespace kernel_module.so compiled at version >= 1.0.0
* Checking an active user.
* Checking registered users equal to 2.
Greybel produces this:
decompiling source...
searching unsecure values...
Unsafe check: loop in array send_bitscount. Buffer overflow.
Unsafe check: string copy in thisCanvasGroupalpha. Buffer overflow.
* Checking registered users equal to 2.
* Checking an active user.
Unsafe check: string copy in var. Buffer overflow.
* Using namespace kernel_module.so compiled at version >= 1.0.0.0
* Checking registered users equal to 5.
* Checking an active user.
* Checking root active user.
The string returned from
scan_address
in GreyHack places a\n\n
after each vulnerability. Greybel does not.This is significant because the existence of the double newline allows you to easily split the string into a list of separate attacks.
For example, GreyHack produces the following:
Greybel produces this: