PatchTheCVEcitrusdb vulnerabilities
Recent CVEs affecting citrusdb products. 5 tracked.
citrusdb has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 4. Most recent: 2005-04-27. Highest priority: CVE-2005-0408 (score 67/100).
- CVE-2005-0411 HIGH 7.5 UPGRADE Directory traversal vulnerability in index.php for CitrusDB 0.3.6 and earlier allows remote attackers and loca
- CVE-2005-0410 MEDIUM 5.0 UPGRADE SQL injection vulnerability in importcc.php for CitrusDB 0.3.6 and earlier allows remote attackers to inject d
- CVE-2005-0409 MEDIUM 6.4 UPGRADE CitrusDB 0.3.6 and earlier does not verify authorization for the (1) importcc.php and (2) uploadcc.php, which
- CVE-2005-0408 CRITICAL 9.8 UPGRADE CitrusDB 0.3.6 and earlier generates easily predictable MD5 hashes of the user name for the id_hash cookie, wh
- CVE-2005-0229 MEDIUM 5.0 DOWNGRADE CitrusDB 0.3.5 and earlier stores the newfile.txt temporary data file under the web root, which allows remote
FAQ
How do I fix citrusdb 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 citrusdb being exploited right now?
None of the tracked citrusdb CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which citrusdb CVE should I patch first?
CVE-2005-0408 currently ranks highest (67/100): CitrusDB 0.3.6 and earlier generates easily predictable MD5 hashes of the user name for the id_hash cookie, wh.