widevine-partner/android
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
152f2144f9f77288a86ae28fc416bf1a8bc4c4a7
android/libwvdrmengine/oemcrypto/odk/test/fuzzing
History
Vicky Min 152f2144f9 Fix ODK warning errors for WV DRM 
PiperOrigin-RevId: 525266553
Merged from https://widevine-internal-review.googlesource.com/169640

Change-Id: Id92dac068a2b2f767287641170f7b522f54588e4
2024-01-29 11:51:41 -08:00
..
corpus/little_endian_64bit
Merge Android odk fuzz changes(Adding corpus) from http://go/wvgerrit/98692
2020-04-27 14:00:17 -07:00
corpus_generator
Merge "Cleanup vendor projects are proprietary." into tm-qpr-dev-plus-aosp am: cbb6177df2
2023-02-05 03:54:39 +00:00
Android.bp
Cleanup vendor projects are proprietary.
2023-02-03 14:37:11 -08:00
odk_fuzz_helper.cpp
Fix ODK warning errors for WV DRM
2024-01-29 11:51:41 -08:00
odk_fuzz_helper.h
Merge latest oemcrypto-v17 change
2022-01-27 20:07:15 -08:00
odk_fuzz_structs.h
Update license comment
2021-04-12 14:10:08 -07:00
odk_license_request_fuzz.cpp
Update license comment
2021-04-12 14:10:08 -07:00
odk_license_response_fuzz_with_mutator.cpp
Update license comment
2021-04-12 14:10:08 -07:00
odk_license_response_fuzz.cpp
Update license comment
2021-04-12 14:10:08 -07:00
odk_provisioning_request_fuzz.cpp
Update license comment
2021-04-12 14:10:08 -07:00
odk_provisioning_response_fuzz_with_mutator.cpp
Fix unused param warnings in oemcrypto fuzz test
2021-04-23 10:11:48 -07:00
odk_provisioning_response_fuzz.cpp
Update license comment
2021-04-12 14:10:08 -07:00
odk_renewal_request_fuzz.cpp
Update license comment
2021-04-12 14:10:08 -07:00
odk_renewal_response_fuzz_with_mutator.cpp
Fix unused param warnings in oemcrypto fuzz test
2021-04-23 10:11:48 -07:00
odk_renewal_response_fuzz.cpp
Update license comment
2021-04-12 14:10:08 -07:00
README.md
Copy submitted odk fuzzing changes from cdm repository to android
2020-04-21 18:42:43 +00:00

README.md

ODK Fuzzing

Objective

  • Run fuzzing on ODK and KDO serialize and deserialize APIs using google supported fuzzer engines to find security vulnerabilities. Any issues found by clusterfuzz will be reported to odk fuzz buganizer.

Run fuzz target on local machine

  • In order to run fuzz target locally and see code coverage, save binary input to be tested against fuzz target into a temporary corpus directory and execute following commands

    $ blaze build --config=asan-fuzzer //your:target
$ blaze-bin/your/target FULL_CORPUS_DIR