Skip to content
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

app-layer-ssl: fix out of bounds memory read #1946

Merged
merged 1 commit into from Mar 18, 2016

Conversation

thus
Copy link
Contributor

@thus thus commented Mar 17, 2016

Added several checks to avoid out of bounds memory read caused
by malformed traffic.
@inliniac inliniac merged commit eb39487 into OISF:master Mar 18, 2016
fooinha added a commit to fooinha/suricata that referenced this pull request Dec 4, 2016
fooinha added a commit to fooinha/suricata that referenced this pull request Dec 17, 2016
fooinha added a commit to fooinha/suricata that referenced this pull request Jan 25, 2017
inliniac pushed a commit that referenced this pull request Jan 26, 2017
At shutdown, all flows that still need work are handled by the flow
force reassembly logic. This means one or more flow end pseudo packets
are generated and pushed through the engine for final detection and
logging.

In some cases this would not work correctly. This was caused by the
flow timeout logic kicking in before all the 'live' packets were
processed. Before the flow timeout handling runs the receive threads
are disabled, however the engine did not wait for the in-flight
packets to be fully processed. In autofp mode, packets could still
be in the queue between receive thread(s) and flow worker(s).

This patch adds a new function that 'drains' all the packet threads
of any in-progress packets before moving on the flow timeout logic.

Bug #1946.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants