<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/sightings/feed</id>
  <title>Most recent sightings.</title>
  <updated>2026-04-30T12:18:55.765496+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent sightings.</subtitle>
  <entry>
    <id>https://db.gcve.eu/sighting/01300f49-72b1-4174-93a2-17185d83633b/export</id>
    <title>01300f49-72b1-4174-93a2-17185d83633b</title>
    <updated>2026-04-30T12:18:56.109218+00:00</updated>
    <author>
      <name>cedric</name>
      <uri>http://db.gcve.eu/user/cedric</uri>
    </author>
    <content>{"uuid": "01300f49-72b1-4174-93a2-17185d83633b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46990", "type": "seen", "source": "https://t.me/cvedetector/6000", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46990 - Directus Localhost Bypass via Loopback Devices\", \n  \"Content\": \"CVE ID : CVE-2024-46990 \nPublished : Sept. 18, 2024, 5:15 p.m. | 40\u00a0minutes ago \nDescription : Directus is a real-time API and App dashboard for managing SQL database content. When relying on blocking access to localhost using the default `0.0.0.0` filter a user may bypass this block by using other registered loopback devices (like `127.0.0.2` - `127.127.127.127`). This issue has been addressed in release versions 10.13.3 and 11.1.0. Users are advised to upgrade. Users unable to upgrade may block this bypass by manually adding the `127.0.0.0/8` CIDR range which will block access to any `127.X.X.X` ip instead of just `127.0.0.1`. \nSeverity: 5.0 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-18T20:05:48.000000Z"}</content>
    <link href="https://db.gcve.eu/sighting/01300f49-72b1-4174-93a2-17185d83633b/export"/>
    <published>2024-09-18T20:05:48+00:00</published>
  </entry>
  <entry>
    <id>https://db.gcve.eu/sighting/cb37986f-0c57-492a-8740-49d071790446/export</id>
    <title>cb37986f-0c57-492a-8740-49d071790446</title>
    <updated>2026-04-30T12:18:56.107947+00:00</updated>
    <author>
      <name>cedric</name>
      <uri>http://db.gcve.eu/user/cedric</uri>
    </author>
    <content>{"uuid": "cb37986f-0c57-492a-8740-49d071790446", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46990", "type": "published-proof-of-concept", "source": "https://t.me/jj_8tl/56", "content": "Short explanation of my CVE-2024-46990 \ud83d\udd25\nThe team of Directus mitigated SSRF by filtering out 127.0.0.1 and localhost. But using CIDR of 127.0.0.0/8 I was able to bypass it and get full SSRF!\nSee my SSRF payloads in the images below \ud83c\udfaf", "creation_timestamp": "2024-11-24T14:15:18.000000Z"}</content>
    <link href="https://db.gcve.eu/sighting/cb37986f-0c57-492a-8740-49d071790446/export"/>
    <published>2024-11-24T14:15:18+00:00</published>
  </entry>
</feed>
