<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T03:33:40.465291+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cve-2019-13115</id>
    <title>CVE-2019-13115</title>
    <updated>2026-11-21T03:33:40.471137+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>In libssh2 before 1.9.0, kex_method_diffie_hellman_group_exchange_sha256_key_exchange in kex.c has an integer overflow that could lead to an out-of-bounds read in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server. This is related to an _libssh2_check_length mistake, and is different from the various issues fixed in 1.8.1, such as CVE-2019-3855.</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2019-13115"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-5308-1</id>
    <title>USN-5308-1 — libssh2 vulnerabilities</title>
    <updated>2026-11-21T03:33:40.471225+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: libssh2</p>
<p>It was discovered that libssh2 mishandled certain input. If libssh2 were
used to connect to a malicious or compromised SSH server, a remote,
unauthenticated attacker could possibly execute arbitrary code on the client 
system. (CVE-2019-3855)</p>
<p>It was discovered that libssh2 incorrectly handled prompt requests. A
remote attacker could possibly use this issue to execute arbitrary code.
(CVE-2019-3856)</p>
<p>It was discovered that libssh2 incorrectly handled SSH_MSG_CHANNEL_REQUEST
packets. A remote attacker could possibly use this issue to execute
arbitrary code, cause a denial of service, or obtain sensitive information. 
(CVE-2019-3857, CVE-2019-3862)</p>
<p>It was discovered that libssh2 incorrectly handled specially crafted SFTP
packets. A remote attacker could possibly use this issue to cause a denial
of service or obtain sensitive information. (CVE-2019-3858)</p>
<p>It was discovered that libssh2 incorrectly handled certain specially
crafted packets. A remote attacker could possibly use this issue to cause a
denial of service or obtain sensitive information. (CVE-2019-3859)</p>
<p>It was discovered that libssh2 incorrectly handled SFTP packets with empty
payloads. A remote attacker could possibly use this issue to cause a denial
of service or obtain sensitive information. (CVE-2019-3860)</p>
<p>It was discovered that libssh2 incorrectly handled padding values in SSH
packets. A remote attacker could possibly use this issue to cause a denial
of service or obtain sensitive information. (CVE-2019-3861)…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-5308-1"/>
  </entry>
</feed>
