gpsdrive vulnerabilities
Recent CVEs affecting gpsdrive products. 4 tracked.
gpsdrive has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2008-12-22. Highest priority: CVE-2008-5704 (score 44/100).
- CVE-2008-5704 HIGH 7.6 UPGRADE src/unit_test.c in gpsdrive (aka gpsdrive-scripts) 2.10~pre4 might allow local users to overwrite arbitrary fi
- CVE-2008-5703 MEDIUM 6.2 UPGRADE gpsdrive (aka gpsdrive-scripts) 2.10~pre4 allows local users to overwrite arbitrary files via a symlink attack
- CVE-2008-5380 MEDIUM 6.9 DOWNGRADE gpsdrive (aka gpsdrive-scripts) 2.09 allows local users to overwrite arbitrary files via a symlink attack on a
- CVE-2008-4959 MEDIUM 6.9 DOWNGRADE geo-code in gpsdrive-scripts 2.10~pre4 allows local users to overwrite arbitrary files via a symlink attack on
FAQ
How do I fix gpsdrive 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 gpsdrive being exploited right now?
None of the tracked gpsdrive CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gpsdrive CVE should I patch first?
CVE-2008-5704 currently ranks highest (44/100): src/unit_test.c in gpsdrive (aka gpsdrive-scripts) 2.10~pre4 might allow local users to overwrite arbitrary fi.