-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
oss-fuzz: stack overflow in pest::parser_state::ParserState<R>::rule
#674
Comments
I had to change my email address over to the primary Google Account email address: google/oss-fuzz#8090 |
As with google#8090 google#8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
As with #8090 #8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
As with google#8090 google#8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
This seems to be recursing around: Line 369 in e30f63e
@CAD97 @NoahTheDuke I guess the simplest fix may be to introduce a recursion depth limit/counter? Given not everyone has access to the original issue, I'll post a part of the stack trace + the minimised sample that could be used to reproduce this issue. a part of stack trace:
minimised sample:
|
reproduced it on older 2.x versions |
one more sample:
|
As with google#8090 google#8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
Describe the bug
Fuzzing found a stack overflow. Detailed report: https://oss-fuzz.com/testcase-detail/4831410241798144
Upstream tracker: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49508
To Reproduce
https://google.github.io/oss-fuzz/advanced-topics/reproducing/
Expected behavior
No stack overflow.
Additional context
crash revision: e30f63e
🙃 I'm getting cc'd at my primary email and can access the oss-fuzz.com details but not the bugs.chromium.org tracker. (google/oss-fuzz#8096)
The text was updated successfully, but these errors were encountered: