You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2022. It is now read-only.
Michael Scherer of Red Hat reports:
While trying to upgrade my F19 to F20 using fedup, I noticed that it use
a directory in /var/tmp/, with a fixed known name.
cachedir = '/var/tmp/fedora-upgrade'
It's actually a download cache; everything that is downloaded there is verified - either by downloading via https (metadata) or checking GPG signatures (RPMs, boot images).
But, sure, I'll move it to /var/cache, which will "fix" this "vulnerability", I guess.
wgwoods
changed the title
edup: /var/tmp/system-upgrade temporary directory creation vulnerability
/var/tmp/system-upgrade temporary directory creation vulnerability
May 15, 2014
So this would allow an attacker to prevent updates from happening, allowing them to then exploit a known vuln after it should have been fixed ("upgrade freeze attack").
My point was this issue would allow a local user to prevent the system from being updated, hence why this issue is worth fixing (from a security perspective).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Michael Scherer of Red Hat reports:
While trying to upgrade my F19 to F20 using fedup, I noticed that it use
a directory in /var/tmp/, with a fixed known name.
cachedir = '/var/tmp/fedora-upgrade'
One note, in fedup 0.8.0 (F20) the directory is now /var/tmp/system-upgrade
As per https://bugzilla.redhat.com/show_bug.cgi?id=1066679
Suggest you use Python mkdtemp():
http://kurt.seifried.org/2012/03/14/creating-temporary-files-securely/
Thanks.
The text was updated successfully, but these errors were encountered: