<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T23:06:46.573160+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-1681</id>
    <title>CVE-2024-1681 — Log Injection Vulnerability in corydolphin/flask-cors</title>
    <updated>2026-09-30T23:06:47.825860+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> corydolphin/flask-cors, corydolphin flask-cors</p>
<p>corydolphin/flask-cors is vulnerable to log injection when the log level is set to debug. An attacker can inject fake log entries into the log file by sending a specially crafted GET request containing a CRLF sequence in the request path. This vulnerability allows attackers to corrupt log files, potentially covering tracks of other attacks, confusing log post-processing tools, and forging log entries. The issue is due to improper output neutralization for logs.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-1681"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-84pr-m4jr-85g5</id>
    <title>GHSA-84pr-m4jr-85g5 — flask-cors vulnerable to log injection when the log level is set to debug</title>
    <updated>2026-09-30T23:06:47.825971+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: flask-cors</p>
<p>corydolphin/flask-cors is vulnerable to log injection when the log level is set to debug. An attacker can inject fake log entries into the log file by sending a specially crafted GET request containing a CRLF sequence in the request path. This vulnerability allows attackers to corrupt log files, potentially covering tracks of other attacks, confusing log post-processing tools, and forging log entries. The issue is due to improper output neutralization for logs.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-84pr-m4jr-85g5"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2024-271</id>
    <title>PYSEC-2024-271</title>
    <updated>2026-09-30T23:06:47.826018+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: flask-cors</p>
<p>corydolphin/flask-cors is vulnerable to log injection when the log level is set to debug. An attacker can inject fake log entries into the log file by sending a specially crafted GET request containing a CRLF sequence in the request path. This vulnerability allows attackers to corrupt log files, potentially covering tracks of other attacks, confusing log post-processing tools, and forging log entries. The issue is due to improper output neutralization for logs.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2024-271"/>
  </entry>
</feed>
