Fix IPv4 octet and mask length overflow (#57) #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
dig
function inData.IP.Addr
uses anInt
accumulator that can overflow while parsing. It is used to parse IPv4 octets as well as IPv4 and IPv6 mask lengths. This change replaces thedig
function with two special-purpose functions:The
octet
function parses IPv4 octets. It checks the maximum bound while parsing so that overflow is not possible.The
maskLen
function parses mask lengths. The maximum bound is passed as an argument (32 for IPv4 and 128 for IPv6), and it checks the maximum bound while parsing so that overflow is not possible. The use ofoption
is refactored to only check for the/
character, so that an invalid mask length after the/
character can cause a parse failure.Note that these functions include the following performance optimizations:
ord
function is used instead ofdigitToInt
, as the range of characters is already checked.go
helper function are given (bang) strictness annotations to help GHC determine that theChar
andInt
values can be unboxed.An unfortunate side effect of this change is that some error messages change.