Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




oss-sec logo oss-sec mailing list archives

Re: CVE request for oCERT advisory 2009-013 (yTNEF/Evolution TNEF)
From: Josh Bressers <bressers () redhat com>
Date: Fri, 6 Nov 2009 14:53:15 -0500 (EST)

----- "Steven M. Christey" <coley () linus mitre org> wrote:
On Wed, 28 Oct 2009, Mark J Cox wrote:


I checked and oCERT don't have a name, so use CVE-2009-3721 for this.

This advisory covers both buffer overflows and path traversal in the same
data field.  While these may stem from "input validation" (as many issues
do), we would typically assign two separate CVE names, since the fix for a
buffer overflow would not necessarily fix the path traversal (or vice
versa).

Unless there's some deeper reason for using a single CVE, I think we should
assign separate CVEs here.  If you agree Mark, we can use CVE-2009-3721 for
the overflow, and you could assign a new CVE for the traversal.


Let's use CVE-2009-3887 for the traversal then.

Thanks.

-- 
    JB


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]