-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Fuzzer-found issue #57237 (buffer boundary condition) #411
Comments
cc @yawkat |
Add a bounds check so that the proper error (EOF) is thrown. Fixes #411
I added a fix @lsf37 FYI, I think this is an upstream issue in jflex too (same as #403). Unfortunately we use a modified skeleton for our own buffer management, so I can't be 100% sure this appears in the default jflex skeleton. But these two bugs happened in the parts that should not be modified. I'm having a hard time working with the jflex build (bazel :/ ), so haven't managed to contribute upstream yet. You may want to take a look at these issues to see if they can be fixed in jflex. |
Interesting. I'll have a look at that, I thought this should be fixed by now, but I might be wrong. |
Add a bounds check so that the proper error (EOF) is thrown. Fixes #411
Looks like there is a buffer read boundary condition that OSSFuzz has found wrt
TOMLParser
:https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57237
I added a (failing) unit test to reproduce
The text was updated successfully, but these errors were encountered: