Skip to content
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

Fix invalid float with no leading integer #120

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

peterzhu2118
Copy link
Member

When fuzzing with AFL there was an inconsistency in parsing floats. Liquid does not allow floats without a leading integer part, but liquid-c will allow a negative float without a leading integer part (e.g. liquid-c will parse -.1 as -0.1). I've added tests for this in liquid.

@@ -109,7 +109,7 @@ const char *lex_one(const char *start, const char *end, lexer_token_t *token)
}
}

if (ISDIGIT(c) || c == '-') {
if (ISDIGIT(c) || (c == '-' && str + 1 < end && ISDIGIT(str[1]))) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will make the strict parser more strict, so could be a breaking change. We should instead use Liquid::Usage.increment to instrument this change to determine if it will break any code in practice. If we determine that it is relied upon, then I think we will need to make the corresponding strict parsing in the ruby liquid gem less strict instead.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened #123 to instrument this usage.

@peterzhu2118 peterzhu2118 mentioned this pull request Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants