oss-sec mailing list archives
Re: Request for CVE for Vulnerability in Tahoe-LAFS 1.9.0
From: Kurt Seifried <kseifried () redhat com>
Date: Thu, 26 Jan 2012 10:11:23 -0700
And that's why I'm wanting people to include source code commit information in their requests (the system works!!! =). On 01/26/2012 08:12 AM, Patrick R McDonald wrote:
On Thu, Jan 26, 2012 at 03:57:14PM +0100, Christian Hoffmann wrote:Hallo Patrick, On 26.01.2012 15:15, Patrick R McDonald wrote:I would like to request a CVE for a vulnerability in Tahoe-LAFS, https://tahoe-lafs.org/pipermail/tahoe-announce/2012-January/000032.html
I think CVE-2012-0051 has already been assigned to this vulnerability.
It is referenced in the Trac ticket (see below) which is mentioned in the above mail archive post, unless I'm confusing things. References: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654 http://seclists.org/oss-sec/2012/q1/135 (initial request) http://seclists.org/oss-sec/2012/q1/158 (CVE assignment) Best regards, Christian HoffmannMy apologies. Thanks for the info and the quick turnaround.
-- Kurt Seifried Red Hat Security Response Team (SRT)
Current thread:
- Request for CVE for Vulnerability in Tahoe-LAFS 1.9.0 Patrick R McDonald (Jan 26)
- Re: Request for CVE for Vulnerability in Tahoe-LAFS 1.9.0 Christian Hoffmann (Jan 26)
- Re: Request for CVE for Vulnerability in Tahoe-LAFS 1.9.0 Patrick R McDonald (Jan 26)
- Re: Request for CVE for Vulnerability in Tahoe-LAFS 1.9.0 Kurt Seifried (Jan 26)
- Re: Request for CVE for Vulnerability in Tahoe-LAFS 1.9.0 Patrick R McDonald (Jan 26)
- Re: Request for CVE for Vulnerability in Tahoe-LAFS 1.9.0 Christian Hoffmann (Jan 26)