PatchTheCVEkolab vulnerabilities
Recent CVEs affecting kolab products. 6 tracked.
kolab has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2010-04-27. Highest priority: CVE-2009-4824 (score 46/100).
- CVE-2009-4824 HIGH 7.5 UPGRADE Unspecified vulnerability in Kolab Webclient before 1.2.0 in Kolab Server before 2.2.3 allows attackers to hav
- CVE-2008-4165 MEDIUM 4.0 DOWNGRADE admin/user/create_user.php in Kolab Groupware Server 1.0.0 places a user password in an HTTP GET request, whic
- CVE-2007-4510 MEDIUM 4.3 UPGRADE DOWNGRADE ClamAV before 0.91.2, as used in Kolab Server 2.0 through 2.2beta1 and other products, allows remote attackers
- CVE-2006-0213 MEDIUM 4.6 UPGRADE Kolab Server 2.0.1, 2.0.2 and development versions pre-2.1-20051215 and earlier, when authenticating users via
- CVE-2005-4828 MEDIUM 6.4 DOWNGRADE Kolab Server 2.0.0 and 2.0.1 does not properly handle when a large email is sent with a "." in the wrong place
- CVE-2004-1997 MEDIUM 4.6 DOWNGRADE DOWNGRADE Kolab stores OpenLDAP passwords in plaintext in the slapd.conf file, which may be installed world-readable, wh
FAQ
How do I fix kolab 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 kolab being exploited right now?
None of the tracked kolab CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which kolab CVE should I patch first?
CVE-2009-4824 currently ranks highest (46/100): Unspecified vulnerability in Kolab Webclient before 1.2.0 in Kolab Server before 2.2.3 allows attackers to hav.