diff options
| -rw-r--r-- | security/vuxml/vuln.xml | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml index 72f829de5b04..20d90e6d90cb 100644 --- a/security/vuxml/vuln.xml +++ b/security/vuxml/vuln.xml @@ -58,6 +58,38 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> + <vuln vid="2383767c-d224-11e8-9623-a4badb2f4699"> + <topic>libssh -- authentication bypass vulnerability</topic> + <affects> + <package> + <name>libssh</name> + <range><ge>0.6</ge><lt>0.7.6</lt></range> + <range><ge>0.8</ge><lt>0.8.4</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml"> + <p>gladiac reports:</p> + <blockquote cite="https://www.libssh.org/2018/10/16/libssh-0-8-4-and-0-7-6-security-and-bugfix-release/"> + <p>libssh versions 0.6 and above have an authentication bypass + vulnerability in the server code. By presenting the server an + SSH2_MSG_USERAUTH_SUCCESS message in place of the + SSH2_MSG_USERAUTH_REQUEST message which the server would expect to + initiate authentication, the attacker could successfully authentciate + without any credentials.</p> + </blockquote> + </body> + </description> + <references> + <url>https://www.libssh.org/2018/10/16/libssh-0-8-4-and-0-7-6-security-and-bugfix-release/</url> + <cvename>CVE-2018-10933</cvename> + </references> + <dates> + <discovery>2018-10-16</discovery> + <entry>2018-10-17</entry> + </dates> + </vuln> + <vuln vid="8c08ab4c-d06c-11e8-b35c-001b217b3468"> <topic>Libgit2 -- multiple vulnerabilities</topic> <affects> |