-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Assertion failure panic when being fed fuzzed input #581
Comments
While slightly different input, it seems this is also fixed with dbaa3a4 (release planned for today). When I patch in |
Hm, I can still reproduce it, even when patching h2 from git. My cargo.toml for the target server looks like
crash.zip is the full file in a zip. I'm not doing anything special to send it over, just |
There's now a new version of cargo, so removing the "patch" and just trying I tried out your your steps and the newer h2 worked for me, at least. |
Huh. I ran a
Maybe it's the way rocket's running it? It's got h2-0.3.8 in the path so I'm fairly sure it's running the latest code. Can you post how you're running it? I am running on a nightly, but even running on stable works fine. |
Here's what I did: I took the hyper repo, I ran in one terminal: RUST_LOG=hyper,h2 cargo run --features full --example hello And then in a separate terminal, I ran: echo "DVBSSSAqIEhUVFAvMi4wDQoNClNNDQoNCgAAKgEAAAAAAKa8jry8vLy8vLy8vLy8vLy8vLy8vLy8vLysvLy8pqampqampqaupqampqampqamJqampqamplpZWVl5WVlXpqampqaAgICAgICAgICAgICAgICA" | base64 -d | nc localhost 3000 This produced the panic message you reported, and then after running |
Yeah, I can reproduce that command working fine now, but
still fails on the same assert as the original. Should I close this issue and re-open one for that? |
I used rocket (0.5.0-rc.1) as a handy test case for this, but I found the bug when fuzzing hyper, and it seems to be in this repo.
To reproduce, feed the uploaded file into a rocket instance (
base64 -d ... | nc localhost 8000
)I just used the hello world, it likely really doesn't matter.
is a full stack trace
The text was updated successfully, but these errors were encountered: