PatchTheCVEbitlbee vulnerabilities and fixes
Recent CVEs affecting bitlbee, with upgrade or downgrade steps. 3 tracked.
bitlbee has 3 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 3. Most recent: 2017-03-14. Highest priority: CVE-2017-5668 (score 61/100).
- CVE-2017-5668 CRITICAL 9.8 UPGRADE UPGRADE bitlbee-libpurple before 3.5.1 allows remote attackers to cause a denial of service (NULL pointer dereference
- CVE-2016-10189 HIGH 7.5 UPGRADE UPGRADE BitlBee before 3.5 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) a
- CVE-2016-10188 CRITICAL 9.8 UPGRADE Use-after-free vulnerability in bitlbee-libpurple before 3.5 allows remote servers to cause a denial of servic
FAQ
How do I fix bitlbee 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 bitlbee being exploited right now?
None of the tracked bitlbee CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which bitlbee CVE should I patch first?
CVE-2017-5668 currently ranks highest (61/100): bitlbee-libpurple before 3.5.1 allows remote attackers to cause a denial of service (NULL pointer dereference .