PatchTheCVEbanu vulnerabilities
Recent CVEs affecting banu products. 3 tracked.
banu has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2012-10-09. Highest priority: CVE-2011-1843 (score 47/100).
- CVE-2012-3505 MEDIUM 5.0 UPGRADE Tinyproxy 1.8.3 and earlier allows remote attackers to cause a denial of service (CPU and memory consumption)
- CVE-2011-1843 MEDIUM 6.8 UPGRADE Integer overflow in conf.c in Tinyproxy before 1.8.3 might allow remote attackers to bypass intended access re
- CVE-2011-1499 LOW 2.6 UPGRADE MITIGATE acl.c in Tinyproxy before 1.8.3, when an Allow configuration setting specifies a CIDR block, permits TCP conne
FAQ
How do I fix banu 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 banu being exploited right now?
None of the tracked banu CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which banu CVE should I patch first?
CVE-2011-1843 currently ranks highest (47/100): Integer overflow in conf.c in Tinyproxy before 1.8.3 might allow remote attackers to bypass intended access re.