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

file_range: avoid integer overflow when figuring out byte range #1908

Closed
wants to merge 1 commit into from

Conversation

@bagder
Copy link
Member

commented Sep 22, 2017

When trying to bump the value with one and the value is already at max,
it causes an integer overflow.

Detected by oss-fuzz:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3465

Assisted-by: Max Dymond (@cmeister2)

file_range: avoid integer overflow when figuring out byte range
When trying to bump the value with one and the value is already at max,
it causes an integer overflow.

Detected by oss-fuzz:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3465

Assisted-by: Max Dymond
@bagder

This comment has been minimized.

Copy link
Member Author

commented Sep 22, 2017

(the oss-fuzz bug URL is not open for the public as of this time, but will be opened later on so I think the URL can be useful to keep)

@bagder

This comment has been minimized.

Copy link
Member Author

commented Sep 22, 2017

The travis failure is unrelated and is fixed in 7c52b12

@bagder bagder closed this in afbdc96 Sep 23, 2017

@bagder bagder deleted the bagder/file-range-overflow branch Sep 23, 2017

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant
You can’t perform that action at this time.