<?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>Sun, 10 May 2026 15:21:05 +0000</lastBuildDate>
    <item>
      <title>63b10fd8-9002-4f68-9eb8-09e22fcfbfb8</title>
      <link>https://vulnerability.circl.lu/sighting/63b10fd8-9002-4f68-9eb8-09e22fcfbfb8/export</link>
      <description>{"uuid": "63b10fd8-9002-4f68-9eb8-09e22fcfbfb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40647", "type": "seen", "source": "https://t.me/cibsecurity/49559", "content": "\u203c CVE-2021-40647 \u203c\n\nIn man2html 1.6g, a specific string being read in from a file will overwrite the size parameter in the top chunk of the heap. This at least causes the program to segmentation abort if the heap size parameter isn't aligned correctly. In version before GLIBC version 2.29 and aligned correctly, it allows arbitrary write anywhere in the programs memory.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-09-09T22:32:38.000000Z"}</description>
      <content:encoded>{"uuid": "63b10fd8-9002-4f68-9eb8-09e22fcfbfb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40647", "type": "seen", "source": "https://t.me/cibsecurity/49559", "content": "\u203c CVE-2021-40647 \u203c\n\nIn man2html 1.6g, a specific string being read in from a file will overwrite the size parameter in the top chunk of the heap. This at least causes the program to segmentation abort if the heap size parameter isn't aligned correctly. In version before GLIBC version 2.29 and aligned correctly, it allows arbitrary write anywhere in the programs memory.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-09-09T22:32:38.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/63b10fd8-9002-4f68-9eb8-09e22fcfbfb8/export</guid>
      <pubDate>Fri, 09 Sep 2022 22:32:38 +0000</pubDate>
    </item>
  </channel>
</rss>
