<?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>Fri, 08 May 2026 13:16:33 +0000</lastBuildDate>
    <item>
      <title>12295c64-d979-4b17-9052-ebbd229faaa7</title>
      <link>https://vulnerability.circl.lu/sighting/12295c64-d979-4b17-9052-ebbd229faaa7/export</link>
      <description>{"uuid": "12295c64-d979-4b17-9052-ebbd229faaa7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-51500", "type": "seen", "source": "https://t.me/cvedetector/9799", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-51500 - Meshtastic firmware Broadcast Address Spoofing Amplification Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-51500 \nPublished : Nov. 4, 2024, 11:15 p.m. | 39\u00a0minutes ago \nDescription : Meshtastic firmware is a device firmware for the Meshtastic project. The Meshtastic firmware does not check for packets claiming to be from the special broadcast address (0xFFFFFFFF) which could result in unexpected behavior and potential for DDoS attacks on the network. A malicious actor could craft a packet to be from that address which would result in an amplification of this one message into every node on the network sending multiple messages. Such an attack could result in degraded network performance for all users as the available bandwidth is consumed. This issue has been addressed in release version 2.5.6. All users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T01:19:11.000000Z"}</description>
      <content:encoded>{"uuid": "12295c64-d979-4b17-9052-ebbd229faaa7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-51500", "type": "seen", "source": "https://t.me/cvedetector/9799", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-51500 - Meshtastic firmware Broadcast Address Spoofing Amplification Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-51500 \nPublished : Nov. 4, 2024, 11:15 p.m. | 39\u00a0minutes ago \nDescription : Meshtastic firmware is a device firmware for the Meshtastic project. The Meshtastic firmware does not check for packets claiming to be from the special broadcast address (0xFFFFFFFF) which could result in unexpected behavior and potential for DDoS attacks on the network. A malicious actor could craft a packet to be from that address which would result in an amplification of this one message into every node on the network sending multiple messages. Such an attack could result in degraded network performance for all users as the available bandwidth is consumed. This issue has been addressed in release version 2.5.6. All users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T01:19:11.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/12295c64-d979-4b17-9052-ebbd229faaa7/export</guid>
      <pubDate>Tue, 05 Nov 2024 01:19:11 +0000</pubDate>
    </item>
  </channel>
</rss>
