-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
jsmn patch: memory access before allocated block #621
Comments
thanks for troubleshooting this issue. Definitely that's the right fix!, I've tested your case and also I've found that it also solves the main issue reported to jsmn here: since JSMN team is not being responsive I will merge this fix directly in our repo and I would like to ask you if you can submit a PR to them too please. |
edsiper
pushed a commit
that referenced
this issue
Jun 7, 2018
This patch also fixes the problem we previously reported in the jsmn repo: zserge/jsmn#131 Signed-off-by: Eduardo Silva <[email protected]>
I've merged the fix into the repo (with your name as author), I will backport this to 0.13 too. thanks! |
edsiper
pushed a commit
that referenced
this issue
Jun 8, 2018
This patch also fixes the problem we previously reported in the jsmn repo: zserge/jsmn#131 Signed-off-by: Eduardo Silva <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
jsmn with the strict allocation patch may create memory access out of bounds. A small input example is
cur.log
fluent-bit.conf
Check with valgrind
Tested on RHEL 7.5.
Patch
With the following patch, valgrind no longer complains, but I have not studied the source code of jsmn so it might require more to fix this issue, like setting
toktype
.The text was updated successfully, but these errors were encountered: