|
Lines 58-63
Notes:
Link Here
|
| 58 |
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.) |
58 |
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.) |
| 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="28bb6ee5-9b5c-11e6-b799-19bef72f4b7c"> |
| 62 |
<topic>node.js -- ares_create_query single byte out of buffer write</topic> |
| 63 |
<affects> |
| 64 |
<package> |
| 65 |
<name>node010</name> |
| 66 |
<range><lt>0.10.48</lt></range> |
| 67 |
</package> |
| 68 |
<package> |
| 69 |
<name>node012</name> |
| 70 |
<range><lt>0.12.17</lt></range> |
| 71 |
</package> |
| 72 |
<package> |
| 73 |
<name>node4</name> |
| 74 |
<range><lt>4.6.1</lt></range> |
| 75 |
</package> |
| 76 |
</affects> |
| 77 |
<description> |
| 78 |
<body xmlns="http://www.w3.org/1999/xhtml"> |
| 79 |
<p>Node.js has released new verions containing the following security fix:</p> |
| 80 |
<blockquote cite="https://nodejs.org/en/blog/vulnerability/october-2016-security-releases/"> |
| 81 |
<p>The following releases all contain fixes for CVE-2016-5180 "ares_create_query single |
| 82 |
byte out of buffer write": Node.js v0.10.48 (Maintenance), Node.js v0.12.17 (Maintenance), |
| 83 |
Node.js v4.6.1 (LTS "Argon") |
| 84 |
</p> |
| 85 |
<p>While this is not a critical update, all users of these release lines should upgrade at |
| 86 |
their earliest convenience. |
| 87 |
</p> |
| 88 |
</blockquote> |
| 89 |
</body> |
| 90 |
</description> |
| 91 |
<references> |
| 92 |
<url>https://nodejs.org/en/blog/vulnerability/october-2016-security-releases/</url> |
| 93 |
<cvename>CVE-2016-5180</cvename> |
| 94 |
</references> |
| 95 |
<dates> |
| 96 |
<discovery>2016-10-18</discovery> |
| 97 |
<entry>2016-10-26</entry> |
| 98 |
</dates> |
| 99 |
</vuln> |
| 100 |
|
| 101 |
<vuln vid="27180c99-9b5c-11e6-b799-19bef72f4b7c"> |
| 102 |
<topic>node.js -- multiple vulnerabilities</topic> |
| 103 |
<affects> |
| 104 |
<package> |
| 105 |
<name>node</name> |
| 106 |
<range><ge>6.0.0</ge><lt>6.9.0</lt></range> |
| 107 |
</package> |
| 108 |
</affects> |
| 109 |
<description> |
| 110 |
<body xmlns="http://www.w3.org/1999/xhtml"> |
| 111 |
<p>Node.js v6.9.0 LTS contains the following security fixes, specific to v6.x:</p> |
| 112 |
<blockquote cite="https://nodejs.org/en/blog/vulnerability/october-2016-security-releases/"> |
| 113 |
<p>Disable auto-loading of openssl.cnf: Don't automatically attempt to load an OpenSSL |
| 114 |
configuration file, from the OPENSSL_CONF environment variable or from the default |
| 115 |
location for the current platform. Always triggering a configuration file load attempt |
| 116 |
may allow an attacker to load compromised OpenSSL configuration into a Node.js process |
| 117 |
if they are able to place a file in a default location. |
| 118 |
</p> |
| 119 |
<p>Patched V8 arbitrary memory read (CVE-2016-5172): The V8 parser mishandled scopes, |
| 120 |
potentially allowing an attacker to obtain sensitive information from arbitrary memory |
| 121 |
locations via crafted JavaScript code. This vulnerability would require an attacker to |
| 122 |
be able to execute arbitrary JavaScript code in a Node.js process. |
| 123 |
</p> |
| 124 |
<p>Create a unique v8_inspector WebSocket address: Generate a UUID for each execution of |
| 125 |
the inspector. This provides additional security to prevent unauthorized clients from |
| 126 |
connecting to the Node.js process via the v8_inspector port when running with --inspect. |
| 127 |
Since the debugging protocol allows extensive access to the internals of a running process, |
| 128 |
and the execution of arbitrary code, it is important to limit connections to authorized |
| 129 |
tools only. Note that the v8_inspector protocol in Node.js is still considered an |
| 130 |
experimental feature. Vulnerability originally reported by Jann Horn. |
| 131 |
</p> |
| 132 |
<p>All of these vulnerabilities are considered low-severity for Node.js users, however, |
| 133 |
users of Node.js v6.x should upgrade at their earliest convenience.</p> |
| 134 |
</blockquote> |
| 135 |
</body> |
| 136 |
</description> |
| 137 |
<references> |
| 138 |
<url>https://nodejs.org/en/blog/vulnerability/october-2016-security-releases/</url> |
| 139 |
<cvename>CVE-2016-5172</cvename> |
| 140 |
</references> |
| 141 |
<dates> |
| 142 |
<discovery>2016-10-18</discovery> |
| 143 |
<entry>2016-10-26</entry> |
| 144 |
</dates> |
| 145 |
</vuln> |
| 146 |
|
| 61 |
<vuln vid="a479a725-9adb-11e6-a298-14dae9d210b8"> |
147 |
<vuln vid="a479a725-9adb-11e6-a298-14dae9d210b8"> |
| 62 |
<topic>FreeBSD -- bhyve - privilege escalation vulnerability</topic> |
148 |
<topic>FreeBSD -- bhyve - privilege escalation vulnerability</topic> |
| 63 |
<affects> |
149 |
<affects> |