Skip to content

Conversation

@MagnusS
Copy link

@MagnusS MagnusS commented Feb 7, 2025

When unsupported fields (such as HE) appear in the header they are not stored in the list of present fields ("kinds"). This may currently panic as the unsupported fields will be ignored and if a VendorNamespace is also present it may be parsed too early in the position of one of the unsupported fields. An invalid length will then end up in skip_length: https://github.com/rossmacarthur/radiotap/blob/trunk/src/lib.rs#L168

This commit adds a new enum for unsupported fields so they can be stored and later skipped during parsing.

Additional bounds checking is also added for VendorNamespace parsing.

When unsupported fields (such as HE) appeared in the header they would not be
stored in "kinds". This resulted in panics as the fields would later be parsed
as VendorNamespace and an invalid length would be stored in skip_length.

This commit adds a new enum for unsupported fields so they can be stored and
later skipped during parsing.

Additional bounds checking is also added for ValueNamespace parsing.
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