<?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>Thu, 28 May 2026 21:20:33 +0000</lastBuildDate>
    <item>
      <title>0b663aa8-2acf-40f8-b15e-59cc0fdee4c8</title>
      <link>https://db.gcve.eu/sighting/0b663aa8-2acf-40f8-b15e-59cc0fdee4c8/export</link>
      <description>{"uuid": "0b663aa8-2acf-40f8-b15e-59cc0fdee4c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-9202", "type": "seen", "source": "https://t.me/cvedetector/6492", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-9202 - Eclipse Dataspace Connector Insecure Dataset Filtering\", \n  \"Content\": \"CVE ID : CVE-2024-9202 \nPublished : Sept. 27, 2024, 10:15 a.m. | 44\u00a0minutes ago \nDescription : In Eclipse Dataspace Components versions 0.1.3 to 0.9.0, the Connector component filters which datasets (= data offers) another party can see in a requested catalog, to ensure that only authorized parties are able to view restricted offers.  \nHowever, there is the possibility to request a single dataset, which should be subject to the same filtering process, but currently is missing the correct filtering.  \n  \n  \nThis enables parties to potentially see datasets they should not have access to, thereby exposing sensitive information. Exploiting this vulnerability requires knowing the ID of a restricted dataset, but some IDs may be guessed by trying out many IDs in an automated way.  \n  \n  \nAffected code:  \n DatasetResolverImpl, L76-79  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T13:22:27.000000Z"}</description>
      <content:encoded>{"uuid": "0b663aa8-2acf-40f8-b15e-59cc0fdee4c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-9202", "type": "seen", "source": "https://t.me/cvedetector/6492", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-9202 - Eclipse Dataspace Connector Insecure Dataset Filtering\", \n  \"Content\": \"CVE ID : CVE-2024-9202 \nPublished : Sept. 27, 2024, 10:15 a.m. | 44\u00a0minutes ago \nDescription : In Eclipse Dataspace Components versions 0.1.3 to 0.9.0, the Connector component filters which datasets (= data offers) another party can see in a requested catalog, to ensure that only authorized parties are able to view restricted offers.  \nHowever, there is the possibility to request a single dataset, which should be subject to the same filtering process, but currently is missing the correct filtering.  \n  \n  \nThis enables parties to potentially see datasets they should not have access to, thereby exposing sensitive information. Exploiting this vulnerability requires knowing the ID of a restricted dataset, but some IDs may be guessed by trying out many IDs in an automated way.  \n  \n  \nAffected code:  \n DatasetResolverImpl, L76-79  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-27T13:22:27.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/0b663aa8-2acf-40f8-b15e-59cc0fdee4c8/export</guid>
      <pubDate>Fri, 27 Sep 2024 13:22:27 +0000</pubDate>
    </item>
  </channel>
</rss>
