<?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://db.gcve.eu</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>Mon, 11 May 2026 04:36:00 +0000</lastBuildDate>
    <item>
      <title>5ece7555-498d-4603-909a-bbdd69a1a5c4</title>
      <link>https://db.gcve.eu/sighting/5ece7555-498d-4603-909a-bbdd69a1a5c4/export</link>
      <description>{"uuid": "5ece7555-498d-4603-909a-bbdd69a1a5c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-30450", "type": "seen", "source": "https://t.me/cibsecurity/61713", "content": "\u203c CVE-2023-30450 \u203c\n\nrpk in Redpanda before 23.1.2 mishandles the redpanda.rpc_server_tls field, leading to (for example) situations in which there is a data type mismatch that cannot be automatically fixed by rpk, and instead a user must reconfigure (while a cluster is turned off) in order to have TLS on broker RPC ports. NOTE: the fix was also backported to the 22.2 and 22.3 branches.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-04-09T02:29:03.000000Z"}</description>
      <content:encoded>{"uuid": "5ece7555-498d-4603-909a-bbdd69a1a5c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-30450", "type": "seen", "source": "https://t.me/cibsecurity/61713", "content": "\u203c CVE-2023-30450 \u203c\n\nrpk in Redpanda before 23.1.2 mishandles the redpanda.rpc_server_tls field, leading to (for example) situations in which there is a data type mismatch that cannot be automatically fixed by rpk, and instead a user must reconfigure (while a cluster is turned off) in order to have TLS on broker RPC ports. NOTE: the fix was also backported to the 22.2 and 22.3 branches.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-04-09T02:29:03.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/5ece7555-498d-4603-909a-bbdd69a1a5c4/export</guid>
      <pubDate>Sun, 09 Apr 2023 02:29:03 +0000</pubDate>
    </item>
  </channel>
</rss>
