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

Bro 2.5.4 #1255

dougburks opened this Issue Jun 5, 2018 · 2 comments


None yet
1 participant

dougburks commented Jun 5, 2018

Bro 2.5.4 primarily fixes security issues:
Multiple fixes and improvements to BinPAC generated code related to array parsing, with potential impact to all Bro’s BinPAC-generated analyzers in the form of buffer over-reads or other invalid memory accesses depending on whether a particular analyzer incorrectly assumed that the evaulated-array-length expression is actually the number of elements that were parsed out from the input.
The NCP analyzer (not enabled by default and also updated to actually work with newer Bro APIs in the release) performed a memory allocation based directly on a field in the input packet and using signed integer storage. This could result in a signed integer overflow and memory allocations of negative or very large size, leading to a crash or memory exhaustion. The new NCP::max_frame_size tuning option now limits the maximum amount of memory that can be allocated.
There’s also the following bug fixes:
A memory leak in the SMBv1 analyzer.
The MySQL analyzer was generally not working as intended, for example, it now is able to parse responses that contain multiple results/rows.


This comment has been minimized.


dougburks commented Jun 6, 2018


This comment has been minimized.

@dougburks dougburks closed this Jun 11, 2018

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