PatchTheCVEbadblue vulnerabilities
Recent CVEs affecting badblue products. 4 tracked.
badblue has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2008-04-28. Highest priority: CVE-2007-6377 (score 56/100).
- CVE-2008-2003 HIGH 7.5 DOWNGRADE BadBlue 2.72 Personal Edition stores multiple programs in the web document root with insufficient access contr
- CVE-2007-6379 MEDIUM 5.0 UPGRADE BadBlue 2.72b and earlier allows remote attackers to obtain sensitive information via an invalid browse parame
- CVE-2007-6378 HIGH 7.5 UPGRADE Directory traversal vulnerability in upload.dll in BadBlue 2.72b and earlier allows remote attackers to create
- CVE-2007-6377 HIGH 7.5 UPGRADE Stack-based buffer overflow in the PassThru functionality in ext.dll in BadBlue 2.72b and earlier allows remot
FAQ
How do I fix badblue 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 badblue being exploited right now?
None of the tracked badblue CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which badblue CVE should I patch first?
CVE-2007-6377 currently ranks highest (56/100): Stack-based buffer overflow in the PassThru functionality in ext.dll in BadBlue 2.72b and earlier allows remot.