[MONGOCRYPT-119] Add fuzz testing to libmongocrypt Created: 07/May/19  Updated: 07/Nov/23

Status: Backlog
Project: Libmongocrypt
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File libfuzzer_entry_point.patch    
Issue Links:
Depends
depends on MONGOCRYPT-186 Implement entry points suitable for l... Backlog
Epic Link: PM-3042

 Description   

Bugs in libmongocrypt mean bugs in all 12 drivers. A fuzzer will give us more coverage for odd edge cases of malformed ciphertexts, key documents, etc.

Stuart has written a guide for setting up the AFL with the C driver.

I envision we'll create small runnable examples that exercise a piece of code to run through the fuzzer. E.g. example-parse-key-document or example-parse-ciphertext.

It'd be great if we could fuzz with evergreen tasks, having the fuzzer run for a fixed period of time.


Generated at Thu Feb 08 09:08:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.