PatchTheCVEbro vulnerabilities and fixes
Recent CVEs affecting bro, with upgrade or downgrade steps. 5 tracked.
bro has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 4. Most recent: 2018-09-13. Highest priority: CVE-2017-1000458 (score 60/100).
- CVE-2018-17019 HIGH 7.5 UPGRADE In Bro through 2.5.5, there is a DoS in IRC protocol names command parsing in analyzer/protocol/irc/IRC.cc.
- CVE-2018-16807 HIGH 7.5 UPGRADE In Bro through 2.5.5, there is a memory leak potentially leading to DoS in scripts/base/protocols/krb/main.bro
- CVE-2017-1000458 CRITICAL 9.8 DOWNGRADE Bro before Bro v2.5.2 is vulnerable to an out of bounds write in the ContentLine analyzer allowing remote atta
- CVE-2015-1522 HIGH 7.5 UPGRADE analyzer/protocol/dnp3/DNP3.cc in Bro before 2.3.2 does not reject certain non-zero values of a packet length,
- CVE-2015-1521 HIGH 7.5 UPGRADE analyzer/protocol/dnp3/DNP3.cc in Bro before 2.3.2 does not properly handle zero values of a packet length, wh
FAQ
How do I fix bro vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is bro being exploited right now?
None of the tracked bro CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which bro CVE should I patch first?
CVE-2017-1000458 currently ranks highest (60/100): Bro before Bro v2.5.2 is vulnerable to an out of bounds write in the ContentLine analyzer allowing remote atta.