Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Mon, 20 May 2013 19:00:41 -0400 (EDT)
From: cve-assign@...re.org
To: gerald@...eshark.org
Cc: cve-assign@...re.org, oss-security@...ts.openwall.com
Subject: CVE assignments for Wireshark 1.8.7 and 1.6.15

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

>8) http://www.wireshark.org/security/wnpa-sec-2013-24.html

Use CVE-2013-3555.


>7) http://www.wireshark.org/security/wnpa-sec-2013-25.html

Use CVE-2013-3556 for the Bug 8599 issue addressed in r48943.

Use CVE-2013-3557 for the Bug 8599 issue addressed in r48944.

It is possible that CVE-2013-3556 only affects people who made their
own builds from the Wireshark trunk, and does not affect users of any
Wireshark release. Although MITRE does not always assign CVE names for
such development-code issues, in this case it is useful for clarifying
the scope of CVE-2013-3557.


>6) http://www.wireshark.org/security/wnpa-sec-2013-26.html

Use CVE-2013-3558.


>5) http://www.wireshark.org/security/wnpa-sec-2013-27.html

Use CVE-2013-3559.


>4) http://www.wireshark.org/security/wnpa-sec-2013-28.html

Use CVE-2013-3560.


>3) http://www.wireshark.org/security/wnpa-sec-2013-29.html

Use CVE-2013-3561 for the Bug 8448 issue. Note that this CVE is shared
with issues covered by wnpa-sec-2013-30 and wnpa-sec-2013-31.

Use CVE-2013-3562 for the Bug 8449 issue.


>2) http://www.wireshark.org/security/wnpa-sec-2013-30.html

Use CVE-2013-3561. Note that this CVE is shared with issues covered by
wnpa-sec-2013-31 and (part of) wnpa-sec-2013-29.


>1) http://www.wireshark.org/security/wnpa-sec-2013-31.html

Use CVE-2013-3561. Note that this CVE is shared with issues covered by
wnpa-sec-2013-30 and (part of) wnpa-sec-2013-29.


>9) http://www.wireshark.org/security/wnpa-sec-2013-23.html

>   Further Note regarding 9):
>   The CVE-2013-2486 && CVE-2013-2487 identifiers
>   have been originally assigned for the 9) issue for the
>   fix in v1.8.6. The patch should contain two patches,
>   but only one was applied. Not sure if a new CVE identifier
>   should be assigned for this case.

See comment 13 in Wireshark bug 8364. CVE-2013-2486 is about revision
47805, and CVE-2013-2487 is about revision 47808 (an issue with a
different discoverer than 47805). MITRE will later publish an update
to the information about affected versions within our CVE-2013-2486
description.

- -- 
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.11 (SunOS)

iQEcBAEBAgAGBQJRmqrWAAoJEGvefgSNfHMdVh4IAI/dNMaSwwJeaxSNybuk0aLd
sgfat0n3gWsjc9gvtmovzXs0gd5VpfKk2ObvTWCuJnIyhyDW5nGgPd1Bj+Qs46/t
6JTcdud0UXfuzjGU2O1OlrRpX8YxqpUNP8RJfgwDSWGeijlE0W5j3/nVBCCwzoHO
QyPARoC92dS0Vi6HOsDljHJHamGLL48X1+b10y6KxR4Q3g6s78fKjottI9THrUUj
F5m8oNIb90FI6luIf7zW6egNR4uNvULjJOiLbLCZvvKn+9+82legQsAy9STwph2q
QIcDuGyGqL06QSKubjYyafog1WWnhk/+dwdQcP2/Z3iK5Z3uJi2IMOZFiEanbpg=
=9leG
-----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.