|
Lines 57-62
Link Here
|
| 57 |
|
57 |
|
| 58 |
--> |
58 |
--> |
| 59 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
59 |
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> |
|
|
60 |
<vuln vid="10d14955-0e45-11e5-b6a8-002590263bf5"> |
| 61 |
<topic>strongswan -- Information Leak Vulnerability</topic> |
| 62 |
<affects> |
| 63 |
<package> |
| 64 |
<name>strongswan</name> |
| 65 |
<range><ge>4.3.0</ge><lt>5.3.2</lt></range> |
| 66 |
</package> |
| 67 |
</affects> |
| 68 |
<description> |
| 69 |
<body xmlns="http://www.w3.org/1999/xhtml"> |
| 70 |
<p>strongSwan Project reports:</p> |
| 71 |
<blockquote cite="http://www.strongswan.org/blog/2015/06/08/strongswan-5.3.2-released.html"> |
| 72 |
<p>An information leak vulnerability was fixed that, in certain IKEv2 |
| 73 |
setups, allowed rogue servers with a valid certificate accepted by |
| 74 |
the client to trick it into disclosing user credentials (even plain |
| 75 |
passwords if the client accepts EAP-GTC). This was caused because |
| 76 |
constraints against the server's authentication were enforced too |
| 77 |
late. All versions since 4.3.0 are affected.</p> |
| 78 |
</blockquote> |
| 79 |
</body> |
| 80 |
</description> |
| 81 |
<references> |
| 82 |
<cvename>CVE-2015-4171</cvename> |
| 83 |
<url>http://www.strongswan.org/blog/2015/06/08/strongswan-5.3.2-released.html</url> |
| 84 |
</references> |
| 85 |
<dates> |
| 86 |
<discovery>2015-06-08</discovery> |
| 87 |
<entry>2015-06-09</entry> |
| 88 |
</dates> |
| 89 |
</vuln> |
| 90 |
|
| 60 |
<vuln vid="838fa84a-0e25-11e5-90e4-d050996490d0"> |
91 |
<vuln vid="838fa84a-0e25-11e5-90e4-d050996490d0"> |
| 61 |
<topic>redis -- EVAL Lua Sandbox Escape</topic> |
92 |
<topic>redis -- EVAL Lua Sandbox Escape</topic> |
| 62 |
<affects> |
93 |
<affects> |