<?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, 24 Jun 2026 07:03:26 +0000</lastBuildDate>
    <item>
      <title>e7ff397b-d6ba-49d9-96b7-b8d3dc94c152</title>
      <link>https://vulnerability.circl.lu/sighting/e7ff397b-d6ba-49d9-96b7-b8d3dc94c152/export</link>
      <description>{"uuid": "e7ff397b-d6ba-49d9-96b7-b8d3dc94c152", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-45100", "type": "seen", "source": "https://t.me/cibsecurity/34120", "content": "\u203c CVE-2021-45100 \u203c\n\nThe ksmbd server through 3.4.2, as used in the Linux kernel through 5.15.8, sometimes communicates in cleartext even though encryption has been enabled. This occurs because it sets the SMB2_GLOBAL_CAP_ENCRYPTION flag when using the SMB 3.1.1 protocol, which is a violation of the SMB protocol specification. When Windows 10 detects this protocol violation, it disables encryption.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-12-16T07:37:04.000000Z"}</description>
      <content:encoded>{"uuid": "e7ff397b-d6ba-49d9-96b7-b8d3dc94c152", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-45100", "type": "seen", "source": "https://t.me/cibsecurity/34120", "content": "\u203c CVE-2021-45100 \u203c\n\nThe ksmbd server through 3.4.2, as used in the Linux kernel through 5.15.8, sometimes communicates in cleartext even though encryption has been enabled. This occurs because it sets the SMB2_GLOBAL_CAP_ENCRYPTION flag when using the SMB 3.1.1 protocol, which is a violation of the SMB protocol specification. When Windows 10 detects this protocol violation, it disables encryption.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-12-16T07:37:04.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/e7ff397b-d6ba-49d9-96b7-b8d3dc94c152/export</guid>
      <pubDate>Thu, 16 Dec 2021 07:37:04 +0000</pubDate>
    </item>
  </channel>
</rss>
