Windows Support

Open
#503 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, swift

Research direction

Start in Sources/libreprl/libreprl-windows.c, especially the CreatePipe usage around line 195, and trace how the data channel mappings are handled for Windows targets. Check how the target is expected to discover those mappings and whether any existing Windows JS-engine workflow documents this. Done means the reported Windows support blockers are resolved and a Windows target can use the data channels.

Written by the indexing model from the issue text.

Description

It seems like there are some issues with the fuzzer's support of Windows targets. In particular, some of the Win32 API usage like

https://github.com/googleprojectzero/fuzzilli/blob/f31876fff984ef7050adcdbe7f4c8bb3255ed8d0/Sources/libreprl/libreprl-windows.c#L195

is incorrect (CreatePipe returns 0 on failure, not on success). I also notice there isn't anywhere the data channel mappings are actually passed into the target, either via environment variable or CLI args, so I'm curious what the expected way for the target to discover the memory mapping is.

I'm wondering A) whether anyone has successfully used fuzzilli to target a JS engine running on Windows and B) whether there is a plan to support it for this use case? I harnessed a JS engine I'm interested in fuzzing that does run on Windows, but I've run into these issues which are blocking me from moving forward.

Dominant language
Swift
Stars
2.3k
Forks
367
Avg merge
23h 53m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleprojectzero/fuzzilli

All issues in googleprojectzero/fuzzilli

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.