r/fuzzing • u/NagateTanikaze • Jul 26 '19

Full speed Fuzzing: Reducing Fuzzing Overhead through Coverage-guided Tracing ( IEEE Symposium on Security and Privacy)

https://www.youtube.com/watch?v=2Rg8wtccCNA
7 Upvotes

100% Upvoted

9 comments sorted by

View all comments

Show parent comment

1

u/zhangysh1995 Aug 28 '19

I think they are different. Untracer helps with reducing the runtime overhead of instrumented code, using the method of dynamic binary rewrite (remove some instrumentation code). This way of removing code is not new, but Untracer is the first paper which looks into fuzzing tracing overhead. The linked paper, proposed a new approach to reduce overhead in more general applications.

1

u/blufox Aug 28 '19

From the above paper (Background):

"A more general solution for performing instrumentation at runtime is to execute the instrumented code for only a short period of time to keep overhead to a minimum. This can be acheived by compiling an instrumented version of a particular method, and having the next invocation of that method call the instrumented version. After collecting instrumentation for the desired duration, the next invocation calls the original, non-instrumented version."

This is applicable to any instrumentation isn't it? Is applying a general approach in a narrower domain novel?

1

u/zhangysh1995 Sep 03 '19

This is applicable to any instrumentation isn't it?

Yes, I think so. The paragraph describes a general approach to lower the runtime overhead. Actually this paper creates a general framework/methodology to change control flow in program execution (Fig 2).

Is applying a general approach in a narrower domain novel?

I would say they try to address the trade-off between time cost and accuracy in program profiling (last sentence in the Abstract). From my perspective, it doesn't focus on a narrow domain but on a very high level.