oxagast/ansvif

A Not So Very Intelligent Fuzzer: An advanced fuzzing framework designed to find vulnerabilities in C/C++ code.

ansvif's Issues

Can't build ansvif, 'fault_code was not declared in this scope'

Hello, everytime when I want to build ansvif, I get error: ‘fault_code’ was not declared in this scope when running aclocal && autoconf && automake -a && ./configure --enable-syscalls && make

Here is the full Bashlog:
https://pastebin.com/5DbEdnyC

uname -a: Linux mercury 4.17.0-kali3-amd64 #1 SMP Debian 4.17.17-1kali1 (2018-08-21) x86_64 GNU/Linux

Make Error src/match_fault.cpp:16:26: fatal error: cryptopp/hex.h: No such file or directory

I have a problem how to fix it ?

Error:

src/match_fault.cpp:16:26: fatal error: cryptopp/hex.h: No such file or directory
compilation terminated.
Makefile:681: recipe for target 'src/ansvif-match_fault.o' failed
make: *** [src/ansvif-match_fault.o] Error 1

Photo:
https://image.ibb.co/m9ZigG/Screenshot_2017_10_02_23_41_37.png

Issues running ansvif on Windows and Ubuntu in a Docker container

When trying to run ansvif in a docker container, I get the error This account is currently not available. Similarly, when trying to run ansvif on Windows, I get the error The process cannot access the file because it is being used by another process.

Code to reproduce error in Docker using a Dockerfile:

FROM ubuntu:16.04

WORKDIR /src

RUN apt update && apt-get --no-install-recommends -yqq install \
	ca-certificates \
	git \
	automake \
	autoconf-archive \
	zlib1g-dev \
	g++ \
	libgcc-4.8-dev \
	gcc \
	gtk2.0

RUN git clone https://github.com/oxagast/ansvif.git
WORKDIR ansvif
RUN	aclocal
RUN autoconf
RUN automake -a
RUN ./configure --disable-gtk
RUN make
CMD make check

Command used to reproduce error in Windows:

.\ansvif.exe -t .\examples\specific\spac
e.txt -c .\notepad.exe -b 2048

I copied notepad into the ansvif folder that was created from the zip on the releases page.

Timeout doesn't work

I haven't been able to get the thread timeout to work yet. The intended behavior is running the to be fuzzed thread which spawns X in /bin/sh, grabbing the PID of the process, then calling the grim reaper function which runs a kill switch on it after a set amount of time. If anybody has a working solution or patch, please let me know.

Thanks.