gpsdrive creates multiple insecure tempfiles, as referenced at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508597 A few of the issues appear to be fixed upstream, specifically for scripts/gpssmswatch and src/splash.c, however src/unit_test.c still references /tmp/gpsdrive-unit-test. gpsdrive-2.10_pre5 and gpsdrive-2.09-r1 appear to suffer from these issues. Reproducible: Always
CVE-2008-5380 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-5380): gpsdrive (aka gpsdrive-scripts) 2.09 allows local users to overwrite arbitrary files via a symlink attack on an (a) /tmp/geo#####, a (b) /tmp/geocaching.loc, a (c) /tmp/geo#####.*, or a (d) /tmp/geo.* temporary file, related to the (1) geo-code and (2) geo-nearest scripts, different vectors than CVE-2008-4959.
CVE-2008-4959 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-4959): geo-code in gpsdrive-scripts 2.10~pre4 allows local users to overwrite arbitrary files via a symlink attack on (1) /tmp/geo.google, (2) /tmp/geo.yahoo, (3) /tmp/geo.coords, and (4) /tmp/geo#####.coords temporary files. CVE-2008-5703 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-5703): gpsdrive (aka gpsdrive-scripts) 2.10~pre4 allows local users to overwrite arbitrary files via a symlink attack on the (a) /tmp/.smswatch or (b) /tmp/gpsdrivepos temporary file, related to (1) examples/gpssmswatch and (2) src/splash.c, different vectors than CVE-2008-4959 and CVE-2008-5380. CVE-2008-5704 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-5704): src/unit_test.c in gpsdrive (aka gpsdrive-scripts) 2.10~pre4 might allow local users to overwrite arbitrary files via a symlink attack on the /tmp/gpsdrive-unit-test/proc temporary file, a different vector than CVE-2008-4959 and CVE-2008-5380.
all thats required here is the removal of app-misc/gpsdrive-2.09-r1?
New version is in portage ... Can this be closed?
Only new versions in portage, no affected around, just ~package. Security please close this :)
Thanks, everyone. Closing noglsa for ~arch-only package.