Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upCrashes in `promql.ParseMetricSelector()` #939
Comments
This comment has been minimized.
This comment has been minimized.
|
Whoa, pasting |
juliusv
added a commit
that referenced
this issue
Jul 29, 2015
juliusv
referenced this issue
Jul 29, 2015
Merged
Fix lexer bug treating non-Latin Unicode digits as digits. #942
This comment has been minimized.
This comment has been minimized.
|
Hah. So this symbol is an Arabic 9, which is categorized as a digit by http://play.golang.org/p/TsuLx8f2pO Same for the other "digits" in the Arabic Unicode block: https://en.wikipedia.org/wiki/Arabic_(Unicode_block) This throws off our parser because we use Filed #942 to fix this. I definitely learned something new today. |
juliusv
closed this
in
#942
Jul 29, 2015
This comment has been minimized.
This comment has been minimized.
|
@msiebuhr Btw., were you inspired by this Fuzz-athon? https://groups.google.com/forum/#!topic/golang-nuts/4PmyYvcnpIs |
gouthamve
pushed a commit
to gouthamve/promql
that referenced
this issue
Mar 28, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
msiebuhr commentedJul 28, 2015
After fuzzing
ParseMetricSelector()for a few hundred iterations (see #667 (comment)), it is found to crash on inputs.٩,G.٩and.٩٩٩٩٩٩٩٩٩٩٩٩٩٩٩٩٩.The first two lead to errors in the lexer and the latter hangs the parser (i.e. it takes more than 10s to complete; the limit looks to be imposed by go-fuzz).
See