oss-sec mailing list archives
Re: CVEs for nginx
From: "Steven M. Christey" <coley () linus mitre org>
Date: Mon, 23 Nov 2009 17:50:28 -0500 (EST)
On Mon, 23 Nov 2009, Josh Bressers wrote:
3.) nginx SSL Renegotiation: http://sysoev.ru/nginx/patch.cve-2009-3555.txt I know the last one contains a CVE number, nginx uses openssl and the patch will disable renegotiation, maybe this deserves an own CVE?We'll use the same ID. mod_ssl did a similar thing and used CVE-2009-3555. I think multiple IDs in this instance would actually create more confusion that it would solve.
The same core problem could be solved any number of ways, and I don't think that should distract from the fact that there is just one core problem. So using the same CVE is appropriate. (Now, if an interim fix is later found to have its own vulns or be bypassed in a way that was not originally advertised, that might need its own CVE.) - Steve
Current thread:
- CVEs for nginx Craig (Nov 19)
- Re: CVEs for nginx Jan Lieskovsky (Nov 23)
- Re: CVEs for nginx Igor Sysoev (Nov 23)
- Re: CVEs for nginx Jan Lieskovsky (Nov 23)
- Re: CVEs for nginx Igor Sysoev (Nov 23)
- Re: CVEs for nginx Igor Sysoev (Nov 23)
- Re: CVEs for nginx Jan Lieskovsky (Nov 23)
- Re: CVEs for nginx Josh Bressers (Nov 23)
- Re: CVEs for nginx Steven M. Christey (Nov 23)
