* Moritz Mühlenhoff:
>> Working on 2.6.1, but I need to get broker (and a new upstream versio
>> nof actor-framework) into unstable first. Working on that, too.
It's a pity that this did not work out...
> With buster being in full freeze, can you backport CVE-2018-17019 and
> CVE-2018-16807 to 2
On Tue, Jan 29, 2019 at 02:19:20AM +0100, Hilko Bengen wrote:
> * Moritz Mühlenhoff:
>
> >> CVE-2018-17019[0]:
> >> | In Bro through 2.5.5, there is a DoS in IRC protocol names command
> >> | parsing in analyzer/protocol/irc/IRC.cc.
> >
> > ping, can we get this one (and CVE-2018-16807) uploaded s
* Hilko Bengen:
>>> | In Bro through 2.5.5, there is a DoS in IRC protocol names command
>>> | parsing in analyzer/protocol/irc/IRC.cc.
>>
>> ping, can we get this one (and CVE-2018-16807) uploaded still in time
>> for buster?
>
> Working on 2.6.1, but I need to get broker (and a new upstream vers
* Moritz Mühlenhoff:
>> CVE-2018-17019[0]:
>> | In Bro through 2.5.5, there is a DoS in IRC protocol names command
>> | parsing in analyzer/protocol/irc/IRC.cc.
>
> ping, can we get this one (and CVE-2018-16807) uploaded still in time
> for buster?
Working on 2.6.1, but I need to get broker (and
On Thu, Sep 13, 2018 at 10:39:17PM +0200, Salvatore Bonaccorso wrote:
> Source: bro
> Version: 2.5-1
> Severity: important
> Tags: patch security upstream
> Control: found -1 2.5.5-1
>
> Hi,
>
> The following vulnerability was published for bro.
>
> CVE-2018-17019[0]:
> | In Bro through 2.5.5, t
Source: bro
Version: 2.5-1
Severity: important
Tags: patch security upstream
Control: found -1 2.5.5-1
Hi,
The following vulnerability was published for bro.
CVE-2018-17019[0]:
| In Bro through 2.5.5, there is a DoS in IRC protocol names command
| parsing in analyzer/protocol/irc/IRC.cc.
If you
6 matches
Mail list logo
