yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #22502
[Bug 1341954] Re: suds client subject to cache poisoning by local attacker
** Also affects: cinder/icehouse
Importance: Undecided
Status: New
** Changed in: cinder/icehouse
Status: New => Fix Committed
** Changed in: cinder/icehouse
Milestone: None => 2014.1.3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1341954
Title:
suds client subject to cache poisoning by local attacker
Status in Cinder:
Fix Released
Status in Cinder havana series:
Fix Released
Status in Cinder icehouse series:
Fix Committed
Status in Gantt:
New
Status in OpenStack Compute (Nova):
Fix Committed
Status in Oslo VMware library for OpenStack projects:
Fix Released
Status in OpenStack Security Advisories:
Won't Fix
Status in OpenStack Security Notes:
New
Bug description:
The suds project appears to be largely unmaintained upstream. The default cache implementation stores pickled objects to a predictable path in /tmp. This can be used by a local attacker to redirect SOAP requests via symlinks or run a privilege escalation / code execution attack via a pickle exploit.
cinder/requirements.txt:suds>=0.4
gantt/requirements.txt:suds>=0.4
nova/requirements.txt:suds>=0.4
oslo.vmware/requirements.txt:suds>=0.4
The details are available here -
https://bugzilla.redhat.com/show_bug.cgi?id=978696
(CVE-2013-2217)
Although this is an unlikely attack vector steps should be taken to
prevent this behaviour. Potential ways to fix this are by explicitly
setting the cache location to a directory created via
tempfile.mkdtemp(), disabling cache client.set_options(cache=None), or
using a custom cache implementation that doesn't load / store pickled
objects from an insecure location.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1341954/+subscriptions