-
Notifications
You must be signed in to change notification settings - Fork 106
Document Error #251
Copy link
Copy link
Closed
Description
Hi, i'm sangjun.
I think there is an error in kAFL hypercall API document.
https://intellabs.github.io/kAFL/reference/hypercall_api.html
it should be changed. i guess so.
kAFL_hypercall(HYPERCALL_KAFL_DUMP_FILE, (uint64_t)&dump_file);
because QEMU-PT recieve structure format through hypercall args1
static void handle_hypercall_kafl_dump_file(struct kvm_run *run,
CPUState *cpu,
uint64_t hypercall_arg)
{
kafl_dump_file_t file_obj;
char filename[256] = { 0 };
char *host_path = NULL;
FILE *f = NULL;
uint64_t vaddr = hypercall_arg;
memset((void *)&file_obj, 0, sizeof(kafl_dump_file_t));
if (!read_virtual_memory(vaddr, (uint8_t *)&file_obj, sizeof(kafl_dump_file_t),
cpu))
{
nyx_error("Failed to read file_obj in %s. Skipping..\n", __func__);
goto err_out1;
}
....
...
...
**However,
Also, I would like to ask another question with different content than this one.
There is a work that created a new fuzzer custom based on kAFL and found many bugs.
Could you please refer to related work in kAFL, just as you reference related work in syzkaller?**
In order for kAFL to be shared more actively as an open source project, I think it would be good to have related work based on kAFL.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
