Skip to content

Conversation

@pallas
Copy link
Contributor

@pallas pallas commented Nov 3, 2018

No description provided.

Derrick Pallas added 3 commits October 2, 2018 13:57
A malformed IP6Address, i.e. with more than 8 components, will cause the
memmove/memset at the end of parsing to fail.  This code is supposed to move
the post-:: bytes to the end of the address and zero out the bytes in the
center.  Instead, it moves some of the bytes the wrong way, potentially
writing prior to parts[] and then zeroing with a negative size.

Instead, make the parser stop when it hits 8 components and let parse figure
out that we did not consume the entire String.

Thanks: American Fuzzy Lop

Change-Id: I2966cb22fb5b44eb9e92dfc6a94e891cf5d02fa7
The check here appears to be intended to make sure that we only connect if
both indexes are valid; specifically, idx can be -1.  Unfortunately, it
checks (*cp)[0] twice.  Instead, check (*cp)[1] too.

Thanks, American Fuzzy Lop

Change-Id: I5cdeb45ac0cef5bbb0a18c6f19b4540df8007bfe
…Packet::data

These two uint16_ts may end up placed at arbitrary offsets into a packet.
In order to generate proper unaligned read/write instructions, mark the
struct as packed.

This was exposed by Defensic suite IPv4 Header Fragment-offset, test 45067
and discovered by Waldin Stone.  I verified it by asserting proper alignment
of ChunkLinks and found that they were not always properly aligned.
@pallas pallas force-pushed the ipreassembler-packing branch from 56437aa to 8ad7a0f Compare November 3, 2018 16:56
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.

1 participant