Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <201403281918.s2SJIGe9011855@linus.mitre.org>
Date: Fri, 28 Mar 2014 15:18:16 -0400 (EDT)
From: cve-assign@...re.org
To: abn@...hat.com
Cc: cve-assign@...re.org, oss-security@...ts.openwall.com
Subject: Re: CVE Split: CVE-2014-0050 Apache Commons FileUpload and Apache Tomcat DoS

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Although Commons FileUpload and Tomcat are affected by this flaw and
> the vulnerable classes share the same ancestry, the code bases for
> them have been maintained in separate source trees for a long while
> now.
> 
> Can this CVE be split?

The existence of separate source trees does not affect the number of
CVE IDs.

> http://seclists.org/fulldisclosure/2014/Feb/41

"Apache Tomcat 7 and Apache Tomcat 8 use a packaged renamed copy of
Apache Commons FileUpload" in that reference is sufficient for us to
use only one CVE ID. We do not rely on factors such as whether the
code has become non-identical or whether different persons are
maintaining the two copies of the code.

- -- 
CVE assignment team, MITRE CVE Numbering Authority
M/S M300
202 Burlington Road, Bedford, MA 01730 USA
[ PGP key available through http://cve.mitre.org/cve/request_id.html ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (SunOS)

iQEcBAEBAgAGBQJTNcoqAAoJEKllVAevmvmsSDMH/3G6KpgE8KkqoeA0G90Dussz
EEwfBy1qxm7s6DMZNn+gmHi2v0cvH6WzbHAcMc01X8noQsFYMkK93ir7Gp1PMFSN
5AdepR+RedtZKKYKOmjCvkOYG0LFH+lUDn+jcsPuqcFZ4zi8jVAP4Q2RHXTpg9VI
xm+gDGkKi3LegOygKkjVnXsr6PHxz7Z7Pzd27KhrK+Qk3wQmTkvAqotXTRJzXFj4
eC6tfwUHoTCO0QZ24RYk+oJaOmk1WlWtLZnsIlzB7rba8Vsb18f0LlT3Eqozz+ha
t5q2veIYA/CDawuPzcvAfSXbqfVtws9HgXs+pJti7CNi4+LQnxCvhbu2mKqhsNQ=
=mlQ2
-----END PGP SIGNATURE-----

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.