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

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
1 participant
Owner

bagder 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
Owner

bagder 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)

Owner

bagder 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment