[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMMrfH4T32hcTG3kO_Ss8G4eXLkCwtMbsVpLwze3hx+NUVBzpg@mail.gmail.com>
Date: Wed, 2 Jul 2014 11:37:16 -0400
From: Brian Harring <ferringb@...il.com>
To: oss-security@...ts.openwall.com
Cc: cve-assign@...re.org, misc@...b.org
Subject: Re: Re: Ansible CVE requests
On Wed, Jul 2, 2014 at 11:08 AM, Florian Weimer <fweimer@...hat.com> wrote:
> On 07/02/2014 04:49 PM, cve-assign@...re.org wrote:
>
>> Additional CVE IDs (at least two) will be assigned for:
>>
>> A. The 2014-06-25 ansible-announce "Ansible 1.6.5 - updated security
>> fix" message at
>> https://groups.google.com/forum/message/raw?msg=ansible-
>> announce/A1px5egCnGQ/jH6f5HM7kpkJ
>>
>
> I think the change in 1.6.5 was an attempt to fix a functionality
> regression, not something that actually added restrictions to the sandbox.
> I am aware that this assessment is at odds with what upstream has stated,
> so you might want to assign a CVE nevertheless.
The change in 1.6.5 was in response to new vulnerabilities I reported- it's
a separate CVE.
Thanks-
~brian
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
