[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-08-14 Thread Launchpad Bug Tracker
This bug was fixed in the package libimobiledevice - 1.1.4-1ubuntu6.2 --- libimobiledevice (1.1.4-1ubuntu6.2) raring-security; urgency=low * SECURITY UPDATE: insecure /tmp usage (LP: #1164263) - debian/patches/CVE-2013-2142.patch: fall back to getpwuid_r instead of using

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-08-14 Thread Launchpad Bug Tracker
This bug was fixed in the package libimobiledevice - 1.1.4-1ubuntu3.2 --- libimobiledevice (1.1.4-1ubuntu3.2) quantal-security; urgency=low * SECURITY UPDATE: insecure /tmp usage (LP: #1164263) - debian/patches/CVE-2013-2142.patch: fall back to getpwuid_r instead of using

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-06-06 Thread Marc Deslauriers
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-2142 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1164263 Title: user-specific and possible

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-05-31 Thread Marc Deslauriers
The directories don't seem to be created in a safe manner though. On Ubuntu, an attack would be prevented by the Yama symlink restrictions, but this is definitely an issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-05-31 Thread Marc Deslauriers
I have reproduced this with an iPod in saucy. Caused by this upsteam commit: http://cgit.sukimashita.com/libimobiledevice.git/commit/src?id=825da48d2e9c20086c4e34869da0b28376676b4c I don't believe there's anything confidential in that directory though, it seems to simply consist of the device's

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-05-31 Thread Marc Deslauriers
Upstream bug: http://libiphone.lighthouseapp.com/projects/27916-libiphone/tickets/331-insecure-tmp-directory-use ** Changed in: libimobiledevice (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-04-07 Thread Paul Collins
** Changed in: libimobiledevice (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1164263 Title: user-specific and possible private

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-04-04 Thread Marc Deslauriers
What user owned those files? Did you perhaps run some of those tools with sudo, or from root without a $HOME directory set? Could you give exact steps necessary to reproduce the issue? ** Information type changed from Private Security to Public Security ** Changed in: libimobiledevice

[Bug 1164263] Re: user-specific and possible private files are written to a global location

2013-04-04 Thread Paul Collins
The files are owned by root. I have not directly run any of the related tools as root (or indeed ever, that I can recall). I can create a fresh set simply by removing the existing set and plugging in my phone: $ ls -lRa /tmp/root /tmp/root: total 12 drwxr-xr-x 3 root root 4096 Apr 4 16:31 ./