|
Lines 58-63
Link Here
|
| 58 |
|
58 |
|
| 59 |
--> |
59 |
--> |
| 60 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
60 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
|
|
61 |
<vuln vid="4caf01e2-30e6-11e5-a4a5-002590263bf5"> |
| 62 |
<topic>libidn -- out-of-bounds read issue with invalid UTF-8 input</topic> |
| 63 |
<affects> |
| 64 |
<package> |
| 65 |
<name>libidn</name> |
| 66 |
<range><lt>1.3.1</lt></range> |
| 67 |
</package> |
| 68 |
</affects> |
| 69 |
<description> |
| 70 |
<body xmlns="http://www.w3.org/1999/xhtml"> |
| 71 |
<p>Simon Josefsson reports:</p> |
| 72 |
<blockquote cite="http://git.savannah.gnu.org/cgit/libidn.git/plain/NEWS?id=libidn-1-31"> |
| 73 |
<p>stringprep_utf8_to_ucs4 now rejects invalid UTF-8. This function |
| 74 |
has always been documented to not validate that the input UTF-8 |
| 75 |
string is actually valid UTF-8. Like the rest of the API, when you |
| 76 |
call a function that works on UTF-8 data, you have to pass it valid |
| 77 |
UTF-8 data. Application writers appear to have difficulties using |
| 78 |
interfaces designed like that, as bugs triggered by invalid UTF-8 |
| 79 |
has been identified in a number of projects (jabberd2, gnutls, wget, |
| 80 |
and curl). While we could introduce a new API to perform UTF-8 |
| 81 |
validation, so that applications can easily implement the proper |
| 82 |
checks, this appear error prone because there is a risk that the |
| 83 |
check will be forgotten. Instead, we took the more radical approach |
| 84 |
of modifying the documentation and the implementation of the API. |
| 85 |
The intention is that all functions that accepts UTF-8 data should |
| 86 |
validate it before use. This will solve the problem for |
| 87 |
applications, without needing to change them. This change has the |
| 88 |
unfortunate side-effect that Surrogate codes (see section 5.5 of RFC |
| 89 |
3454) no longer trigger the STRINGPREP_CONTAINS_PROHIBITED error |
| 90 |
code but instead will trigger the newly introduced |
| 91 |
STRINGPREP_ICONV_ERROR error code, as the gnulib/libunistring-based |
| 92 |
code that we use to test UTF-8-compliance rejects Surrogate codes. |
| 93 |
We hope that this is an acceptable cost to live with in order to |
| 94 |
improve application security. We welcome feedback on this solution, |
| 95 |
and we are marking this release as beta rather than stable to |
| 96 |
signal that we may reconsider this approach if people disagree. |
| 97 |
Reported by several people including Thijs Alkemade, Gustavo Grieco, |
| 98 |
Daniel Stenberg, and Nikos Mavrogiannopoulos.</p> |
| 99 |
</blockquote> |
| 100 |
</body> |
| 101 |
</description> |
| 102 |
<references> |
| 103 |
<cvename>CVE-2015-2059</cvename> |
| 104 |
<url>http://git.savannah.gnu.org/cgit/libidn.git/plain/NEWS?id=libidn-1-31</url> |
| 105 |
</references> |
| 106 |
<dates> |
| 107 |
<discovery>2015-02-09</discovery> |
| 108 |
<entry>2015-07-23</entry> |
| 109 |
</dates> |
| 110 |
</vuln> |
| 111 |
|
| 61 |
<vuln vid="95eee71d-3068-11e5-a9b5-bcaec565249c"> |
112 |
<vuln vid="95eee71d-3068-11e5-a9b5-bcaec565249c"> |
| 62 |
<topic>gdk-pixbuf2 -- heap overflow and DoS affecting Firefox and other programs</topic> |
113 |
<topic>gdk-pixbuf2 -- heap overflow and DoS affecting Firefox and other programs</topic> |
| 63 |
<affects> |
114 |
<affects> |