<?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>Wed, 03 Jun 2026 20:59:01 +0000</lastBuildDate>
    <item>
      <title>2fe5f8e5-b35e-43d1-9625-088254785408</title>
      <link>https://vulnerability.circl.lu/sighting/2fe5f8e5-b35e-43d1-9625-088254785408/export</link>
      <description>{"uuid": "2fe5f8e5-b35e-43d1-9625-088254785408", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42476", "type": "seen", "source": "https://t.me/cvedetector/3274", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42476 - Nim OAuth Library CSRF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42476 \nPublished : Aug. 15, 2024, 7:15 p.m. | 25\u00a0minutes ago \nDescription : In the OAuth library for nim prior to version 0.11, the Authorization Code grant and Implicit grant both rely on the `state` parameter to prevent cross-site request forgery (CSRF) attacks where a resource owner might have their session associated with protected resources belonging to an attacker. When this project is compiled with certain compiler flags set, it is possible that the `state` parameter will not be checked at all, creating a CSRF vulnerability. Version 0.11 checks the `state` parameter using a regular `if` statement or `doAssert` instead of relying on a plain `assert`. `doAssert` will achieve the desired behavior even if `-d:danger` or `--assertions:off` is set. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-15T21:49:32.000000Z"}</description>
      <content:encoded>{"uuid": "2fe5f8e5-b35e-43d1-9625-088254785408", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42476", "type": "seen", "source": "https://t.me/cvedetector/3274", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42476 - Nim OAuth Library CSRF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42476 \nPublished : Aug. 15, 2024, 7:15 p.m. | 25\u00a0minutes ago \nDescription : In the OAuth library for nim prior to version 0.11, the Authorization Code grant and Implicit grant both rely on the `state` parameter to prevent cross-site request forgery (CSRF) attacks where a resource owner might have their session associated with protected resources belonging to an attacker. When this project is compiled with certain compiler flags set, it is possible that the `state` parameter will not be checked at all, creating a CSRF vulnerability. Version 0.11 checks the `state` parameter using a regular `if` statement or `doAssert` instead of relying on a plain `assert`. `doAssert` will achieve the desired behavior even if `-d:danger` or `--assertions:off` is set. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-15T21:49:32.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/2fe5f8e5-b35e-43d1-9625-088254785408/export</guid>
      <pubDate>Thu, 15 Aug 2024 21:49:32 +0000</pubDate>
    </item>
  </channel>
</rss>
