spey vulnerabilities and fixes
Recent CVEs affecting spey, with upgrade or downgrade steps. 3 tracked.
spey has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2007-06-20. Highest priority: CVE-2005-4847 (score 52/100).
- CVE-2007-3298 HIGH 7.5 UPGRADE SQL injection vulnerability in Spey before 0.4.1 allows remote attackers to execute arbitrary SQL commands via
- CVE-2005-4847 HIGH 10.0 DOWNGRADE Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security
- CVE-2005-4846 MEDIUM 4.3 DOWNGRADE Format string vulnerability in Logger.cc for Spey 0.3.3 allows attackers to cause a denial of service (crash)
FAQ
How do I fix spey 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 spey being exploited right now?
None of the tracked spey CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which spey CVE should I patch first?
CVE-2005-4847 currently ranks highest (52/100): Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security.