Re: [EXTERNAL] TRA-2021-14/CVE-2021-20095 status

2021-10-20 Thread Rajiv Motwani
It was an internal discussion about security boundaries that were(n't) crossed as a result of the vulnerability and the decision of the researcher who discovered the issue that a CVE wasn't warranted. Regards, Rajiv On Tue, Oct 19, 2021 at 9:31 PM Salvatore Bonaccorso wrote: > *** CAUTION: This

Re: [EXTERNAL] TRA-2021-14/CVE-2021-20095 status

2021-10-19 Thread Salvatore Bonaccorso
Hi, On Mon, Oct 18, 2021 at 09:58:31AM -0700, Rajiv Motwani wrote: > Hi Sylvain, > > Those CVEs were registered in error and were requested to be listed as > REJECTED. There are no plans to re-register these issues under new > identifiers. Out of interest, can you elaborate on this a bit more? W

Re: [EXTERNAL] TRA-2021-14/CVE-2021-20095 status

2021-10-18 Thread Rajiv Motwani
Hi Sylvain, Those CVEs were registered in error and were requested to be listed as REJECTED. There are no plans to re-register these issues under new identifiers. Regards, Rajiv On Mon, Oct 18, 2021 at 8:54 AM Sylvain Beucler wrote: > *** CAUTION: This email was sent from an EXTERNAL source. T

TRA-2021-14/CVE-2021-20095 status

2021-10-18 Thread Sylvain Beucler
Hello, I'm part of the Debian LTS Team and we would like to track which shipped versions of python-babel are affected by the vulnerability described in your advisory TRA-2021-14. https://fr.tenable.com/security/research/tra-2021-14 The Advisory Timeline shows that CVE-2021-20095 was assigned