oss-sec mailing list archives
Re: Re: Issue with PYTHON_EGG_CACHE
From: Kurt Seifried <kseifried () redhat com>
Date: Mon, 16 Dec 2013 18:59:53 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/16/2013 10:14 AM, Yves-Alexis Perez wrote:
On Sun, Dec 15, 2013 at 02:06:59PM -0700, Kurt Seifried wrote:On 12/15/2013 01:23 PM, Jeremy Stanley wrote:On 2013-12-15 14:47:12 -0500 (-0500), cve-assign () mitre org wrote:This message seems to disclose a vulnerability in an unspecified version of OpenStack Swift.[...]Use CVE-2013-7109 for this report about OpenStack Swift. Again, CVE-2013-7109 is not an ID for which setuptools is the affected product.I don't think this was intended as a CVE request. The OpenStack VMT had already determined this was non-exploitable in Swift over the course of https://launchpad.net/bugs/1192966 and explicitly decided not to request a CVE nor issue an advisory.Sorry yeah I should have been more clear, I was trying to show that it's a pretty common coding pattern to use /tmp for PYTHON_EGG_CACHE, that specific instance was a bad one (it's about the only example where it isn't actually a vulnerability =).Does this mean CVE-2013-7109 should be REJECTed or not? Regards,
Sorry I misspoke, the last week has been not good, I was supposed to be on PTO and instead hurt my back and was taking pain pills, my focus was not so very good. Everything is as it should be CVE wise with respect to PYTHON_EGG_CACHE dir thing. - -- Kurt Seifried Red Hat Security Response Team (SRT) PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBAgAGBQJSr7AZAAoJEBYNRVNeJnmTrd0QAJREAbaXqyZaDWeFY0eKSkxf Lw2PXR0jl0O9D01NySDDCCtggRbfCv36OodNkJhGozFnpKYX00mYtTKcBI0owmuL INfa47i2tqHV0yEY6gDweupjxEy4SaMCIqipe1xNwckbrK92UAn5NBob40EH24CJ UIr49iQZWWWkCnqMykiGQyWJBfXhmtHUCWTXeHcp0C+H3PZa/SHCCmoDLTIzQ2KV KTwgWzHLDJ5hlm+W5PMT1PLDqJMMYXdhOfbgW3EspPHs+EENQYCxhWwvrUVfYIEG +g3Uz55NPO8Nw1I6oLOqzne/K9Wyw36Fy4Gpf2bL7EEAkbt62GZxE4BZqoXsV0Cm e1L3NvuyyliQHN8HNWz6LfqvhzaNb2ICdAerQdoDv9j9MSQ3qt4iJonj2Wi35Znz OvuWU3glR3yrrQ+ScXu91tuvarskXF+u/ebMP0IeflCe5NFJKnSx5CevNtvZn5o3 a1vOsevzkPPi6pkVwD1Sa3dzaj44iXMzgmBQb6+oO+I4bDo2qCQjlu8EZjiHmIeL 2hgiHpoxMqvOO4/7NI0YzRk+nkQ6Ucy+qhhgdbKVZxNtYPlFmqzFQxmvxnL2LHKt qsQe2rLj24QieJZXcxPei7SbVBbw7JKThm8qA2msnLDzP/Jkmh9DnplznLKrwuIP /1urLj7BoVUr9PZcCDX8 =nFWY -----END PGP SIGNATURE-----
Current thread:
- Issue with PYTHON_EGG_CACHE Grant Murphy (Dec 08)
- Re: Issue with PYTHON_EGG_CACHE cve-assign (Dec 09)
- Re: Re: Issue with PYTHON_EGG_CACHE Kurt Seifried (Dec 13)
- Re: Issue with PYTHON_EGG_CACHE cve-assign (Dec 15)
- Re: Re: Issue with PYTHON_EGG_CACHE Jeremy Stanley (Dec 15)
- Re: Re: Issue with PYTHON_EGG_CACHE Kurt Seifried (Dec 15)
- Re: Re: Issue with PYTHON_EGG_CACHE Yves-Alexis Perez (Dec 16)
- Re: Re: Issue with PYTHON_EGG_CACHE Kurt Seifried (Dec 16)
- Re: Re: Issue with PYTHON_EGG_CACHE Yves-Alexis Perez (Dec 17)
- Re: Re: Issue with PYTHON_EGG_CACHE Kurt Seifried (Dec 13)
- Re: Issue with PYTHON_EGG_CACHE cve-assign (Dec 09)