<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 06 May 2026 08:59:50 +0000</lastBuildDate>
    <item>
      <title>a106864c-2031-4ece-bf62-a3539f447642</title>
      <link>https://vulnerability.circl.lu/sighting/a106864c-2031-4ece-bf62-a3539f447642/export</link>
      <description>{"uuid": "a106864c-2031-4ece-bf62-a3539f447642", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-0216-0777", "type": "seen", "source": "https://t.me/ict_security/107", "content": "\ud83d\udcccHow To Patch and Protect OpenSSH Client Vulnerability CVE-2016-0777 and CVE-2016-0778 [ 14/Jan/2016 ]\n\nby Vivek Gite on January 15, 2016 last updated January 16, 2016\n in CentOS, Cryptography, Debian / Ubuntu, FreeBSD, Linux, Openbsd, RedHat and Friends, UNIX\n\nThe OpenSSH project released an ssh client bug info that can leak private keys to malicious servers. A man-in-the-middle kind of attack identified and fixed in OpenSSH are dubbed CVE-2016-0777 and CVE-2016-0778. How do I fix OpenSSH's client vulnerability on a Linux or Unix-like operating system?\nhttp://www.cyberciti.biz/faq/howto-openssh-client-security-update-cve-0216-0777-cve-0216-0778/\n\u2014-------\n\ud83d\udca1\u062f\u0631 \u0632\u0645\u06cc\u0646\u0647 \u0627\u0645\u0646\u06cc\u062a \u0633\u0627\u06cc\u0628\u0631\u06cc \u0628\u0627 \u0634\u0645\u0627 \u062e\u0648\u0627\u0647\u06cc\u0645 \u0628\u0648\u062f.\n\u2705 \u062f\u0631\u06cc\u0627\u0641\u062a \u0622\u062e\u0631\u06cc\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0647\u0627\u06cc \u0627\u0645\u0646\u06cc\u062a \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u062f\u0631 \u06a9\u0627\u0646\u0627\u0644 \n@information_security_management \ud83d\udc48 join \ud83d\udc47\nhttps://telegram.me/joinchat/BaPoBjumXnCYx_E1GT62pw", "creation_timestamp": "2016-01-20T11:57:40.000000Z"}</description>
      <content:encoded>{"uuid": "a106864c-2031-4ece-bf62-a3539f447642", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-0216-0777", "type": "seen", "source": "https://t.me/ict_security/107", "content": "\ud83d\udcccHow To Patch and Protect OpenSSH Client Vulnerability CVE-2016-0777 and CVE-2016-0778 [ 14/Jan/2016 ]\n\nby Vivek Gite on January 15, 2016 last updated January 16, 2016\n in CentOS, Cryptography, Debian / Ubuntu, FreeBSD, Linux, Openbsd, RedHat and Friends, UNIX\n\nThe OpenSSH project released an ssh client bug info that can leak private keys to malicious servers. A man-in-the-middle kind of attack identified and fixed in OpenSSH are dubbed CVE-2016-0777 and CVE-2016-0778. How do I fix OpenSSH's client vulnerability on a Linux or Unix-like operating system?\nhttp://www.cyberciti.biz/faq/howto-openssh-client-security-update-cve-0216-0777-cve-0216-0778/\n\u2014-------\n\ud83d\udca1\u062f\u0631 \u0632\u0645\u06cc\u0646\u0647 \u0627\u0645\u0646\u06cc\u062a \u0633\u0627\u06cc\u0628\u0631\u06cc \u0628\u0627 \u0634\u0645\u0627 \u062e\u0648\u0627\u0647\u06cc\u0645 \u0628\u0648\u062f.\n\u2705 \u062f\u0631\u06cc\u0627\u0641\u062a \u0622\u062e\u0631\u06cc\u0646 \u062a\u0648\u0635\u06cc\u0647 \u0647\u0627\u06cc \u0627\u0645\u0646\u06cc\u062a \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u062f\u0631 \u06a9\u0627\u0646\u0627\u0644 \n@information_security_management \ud83d\udc48 join \ud83d\udc47\nhttps://telegram.me/joinchat/BaPoBjumXnCYx_E1GT62pw", "creation_timestamp": "2016-01-20T11:57:40.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/a106864c-2031-4ece-bf62-a3539f447642/export</guid>
      <pubDate>Wed, 20 Jan 2016 11:57:40 +0000</pubDate>
    </item>
  </channel>
</rss>
