-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes found by honggfuzz #3
Comments
Awesome, this is a great find! It shouldn't ever be crashing tbh, so we should probably fix this! edit: yeah, it should probably be called |
@killercup by the way, do you maybe still have the code for the fuzzer? Would be great if we could check it in for future parts :D |
The code is in rust-fuzz/targets#114 but i can make a PR to add it here too Edit: #5 |
Woah, didn't realize |
* Simplify header tests * Fix typo * Fixes #3: Crashes found by Honggfuzz * No need to verify trailing zeros according to docs * Stricter algorithm name parsing Give up if an unknown algorithm name is encountered. According to docs, the allowed algorithm names are "BLAKE2b", "Ed25519" and "". * Cleanup
Howdy! This is a 🐛 bug report for two crashes I found with the following fuzzer script that you can also find in rust-fuzz/targets#114:
Should this assertion of from_vec¹ -> to_vec -> from_vec hold?
If yes, with
data
as either ofb"\x05\x02W\x01\x00\xb0\xb0\xb0\xb0\xb0\xb0\xb0\xb0\xb0\xb0\xb0\xfb\x03p\xb0\xb0\xb0\xb0\xb0\xb0\xb0\xb0\xbb9\xb0\xf5\xf5"
b"\x05\x02W\x01\x00\x00\x00\x12\x12\x12\x00\x00S\xc3\xcf\x8a2\xcc\xd1\xce9\xc4K\x9343\x00602\xb5\x07"
the current git master crashes. I have not investigated further.
¹ Why is this called
from_vec
when it takes a slice? I'd probably call itfrom_bytes
which is more precise.The text was updated successfully, but these errors were encountered: