Date: Tue, 18 Aug 2015 19:24:48 -0400 (EDT) From: cve-assign@...re.org To: seth.arnold@...onical.com Cc: cve-assign@...re.org, oss-security@...ts.openwall.com, security@...ntu.com Subject: Re: CVE Request: ippusbxd -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > Till Kamppeter has provided the following patches to address the issue: > https://github.com/tillkamppeter/ippusbxd/commit/46844402bca7a38fc224483ba6f0a93c4613203f > https://github.com/tillkamppeter/ippusbxd/commit/a632841f8e65d402e13e81921515f5a1e2736c82 > > The first patch switches to using two sockets and binds them explicitly > to the IPv6 and the IPv4 loopback addresses; the second patch simplifies > the use of select(). Both patches are recommended. As far as we can tell, the message was written this way because you are addressing multiple audiences: one audience is interested in what aspects of the commits are security-related so that they can be mapped to individual CVE IDs, and another audience is much less concerned about these mapping details but wants to fix the security problem without adding a new problem in its place. Specifically, our understanding is that there is no expectation that anyone has a production copy of the code with 46844402bca7a38fc224483ba6f0a93c4613203f but not a632841f8e65d402e13e81921515f5a1e2736c82. If anyone had such a copy, they possibly might find that an attacker could cause a performance degradation via a crafted client that intentionally triggers the "select() call repeated in a loop if the timeout expired without incoming data" issue. In other words, there is no CVE ID for a "repeated in a loop" problem, and probably for two reasons: nobody is using that code, and the performance degradation is too small. > https://bugs.launchpad.net/ubuntu/+source/ippusbxd/+bug/1455644 The only CVE ID is for the presence of "addr.sin6_addr = in6addr_any" in the original code. Use CVE-2015-6520. - -- 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 iQEcBAEBCAAGBQJV071DAAoJEKllVAevmvmsaF0IAIwQQu5Le3ygNRS0luytSxf8 tdqQ19YXjCdlQVSyXbqlRsSul3BMskti3KvsUwLo5zxJZfIwb/npdekT2pkp1g5Y GbJ3jbL70iXf9oSX6G/7arSZWPmrGDpDbeU02pvCxQtLmS5ApqS9OMNOAzp51i5m u9o7yEqnWUMuB0NnIQITonCiAZHuFBruhQ3j3yksKLz0SUl8AevefzBxCurDwaBV vBnEpqc9qvgQIHhvNZ3CfMthTI2tJbDB2oOCqckFxtnsMIS6QcYdBS5X0mla7ilf 7WDzZKFCCAgUAjTZ9Mukhno1cmSLeBNTuEMK6lmoumK0SOlxUgV+weeXTBQHttI= =MhM/ -----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.