[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-USN-5308-1":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T20:55:29.923Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":58,"duplicates":59,"related":60,"reserved_at":9,"published_at":72,"modified_at":73,"state":9,"summary":74,"references_raw":76,"kevs":128,"epss":9,"epss_history":129,"metrics":130,"affected":131},"USN-5308-1","libssh2 vulnerabilities\n\nIt was discovered that libssh2 mishandled certain input. If libssh2 were\nused to connect to a malicious or compromised SSH server, a remote,\nunauthenticated attacker could possibly execute arbitrary code on the client \nsystem. (CVE-2019-3855)\n\nIt was discovered that libssh2 incorrectly handled prompt requests. A\nremote attacker could possibly use this issue to execute arbitrary code.\n(CVE-2019-3856)\n\nIt was discovered that libssh2 incorrectly handled SSH_MSG_CHANNEL_REQUEST\npackets. A remote attacker could possibly use this issue to execute\narbitrary code, cause a denial of service, or obtain sensitive information. \n(CVE-2019-3857, CVE-2019-3862)\n\nIt was discovered that libssh2 incorrectly handled specially crafted SFTP\npackets. A remote attacker could possibly use this issue to cause a denial\nof service or obtain sensitive information. (CVE-2019-3858)\n\nIt was discovered that libssh2 incorrectly handled certain specially\ncrafted packets. A remote attacker could possibly use this issue to cause a\ndenial of service or obtain sensitive information. (CVE-2019-3859)\n\nIt was discovered that libssh2 incorrectly handled SFTP packets with empty\npayloads. A remote attacker could possibly use this issue to cause a denial\nof service or obtain sensitive information. (CVE-2019-3860)\n\nIt was discovered that libssh2 incorrectly handled padding values in SSH\npackets. A remote attacker could possibly use this issue to cause a denial\nof service or obtain sensitive information. (CVE-2019-3861)\n\nIt was discovered that libssh2 incorrectly handled interactive response\nmessages length. A remote attacker could possibly use this issue to execute\narbitrary code. (CVE-2019-3863)\n\nIt was discovered that libssh2 incorrectly handled the Diffie Hellman key\nexchange. A remote attacker could possibly use this issue to cause a denial\nof service or obtain sensitive information. (CVE-2019-13115)\n\nIt was discovered that libssh2 incorrectly handled bound checks in\nSSH_MSG_DISCONNECT. A remote attacker could possibly use this issue to\ncause a denial of service or obtain sensitive information. (CVE-2019-17498)\n",null,[],[],[],[14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56],{"_key":15},"CVE-2019-13115",{"_key":17},"CVE-2019-17498",{"_key":19},"CVE-2019-3855",{"_key":21},"CVE-2019-3856",{"_key":23},"CVE-2019-3857",{"_key":25},"CVE-2019-3858",{"_key":27},"CVE-2019-3859",{"_key":29},"CVE-2019-3860",{"_key":31},"CVE-2019-3861",{"_key":33},"CVE-2019-3862",{"_key":35},"CVE-2019-3863",{"_key":37},"UBUNTU-CVE-2019-13115",{"_key":39},"UBUNTU-CVE-2019-17498",{"_key":41},"UBUNTU-CVE-2019-3855",{"_key":43},"UBUNTU-CVE-2019-3856",{"_key":45},"UBUNTU-CVE-2019-3857",{"_key":47},"UBUNTU-CVE-2019-3858",{"_key":49},"UBUNTU-CVE-2019-3859",{"_key":51},"UBUNTU-CVE-2019-3860",{"_key":53},"UBUNTU-CVE-2019-3861",{"_key":55},"UBUNTU-CVE-2019-3862",{"_key":57},"UBUNTU-CVE-2019-3863",[],[],[61,62,63,64,65,66,67,68,69,70,71],{"_key":37},{"_key":39},{"_key":41},{"_key":43},{"_key":45},{"_key":47},{"_key":49},{"_key":51},{"_key":53},{"_key":55},{"_key":57},"2022-03-07T23:47:01Z","2026-05-20T16:03:19.028889806Z",{"cisa_kev":75,"cisa_ransomware":75,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[77,83,88,92,96,100,104,108,112,116,120,124],{"url":78,"sources":79,"tags":81},"https://ubuntu.com/security/notices/USN-5308-1",[80],"osv_ubuntu",[82],"Advisory",{"url":84,"sources":85,"tags":86},"https://ubuntu.com/security/CVE-2019-3855",[80],[87],"REPORT",{"url":89,"sources":90,"tags":91},"https://ubuntu.com/security/CVE-2019-3856",[80],[87],{"url":93,"sources":94,"tags":95},"https://ubuntu.com/security/CVE-2019-3857",[80],[87],{"url":97,"sources":98,"tags":99},"https://ubuntu.com/security/CVE-2019-3858",[80],[87],{"url":101,"sources":102,"tags":103},"https://ubuntu.com/security/CVE-2019-3859",[80],[87],{"url":105,"sources":106,"tags":107},"https://ubuntu.com/security/CVE-2019-3860",[80],[87],{"url":109,"sources":110,"tags":111},"https://ubuntu.com/security/CVE-2019-3861",[80],[87],{"url":113,"sources":114,"tags":115},"https://ubuntu.com/security/CVE-2019-3862",[80],[87],{"url":117,"sources":118,"tags":119},"https://ubuntu.com/security/CVE-2019-3863",[80],[87],{"url":121,"sources":122,"tags":123},"https://ubuntu.com/security/CVE-2019-13115",[80],[87],{"url":125,"sources":126,"tags":127},"https://ubuntu.com/security/CVE-2019-17498",[80],[87],[],[],[],[132],{"ecosystem":133,"name":134,"vendor":135,"product":134,"cpe_part":9,"purl_type":136,"purl_namespace":135,"purl_name":134,"source":9,"versions":137},"Ubuntu","libssh2","ubuntu","deb",[138],{"version":139,"is_range":140,"range_type":141,"version_start":9,"version_start_type":9,"version_end":142,"version_end_type":143,"fixed_in":9},"lt1_5_0_2ubuntu0_1+esm1",true,"ecosystem","1.5.0-2ubuntu0.1+esm1","excluding"]