<?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 entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 01:50:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-67178 — Open Redirect in MISP Installer-Generated Apache Configuration</title>
      <link>https://db.gcve.eu/vuln/cve-2026-67178</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; misp&lt;/p&gt;
&lt;p&gt;MISP installation scripts generated an Apache HTTP virtual-host configuration containing an incorrectly formatted HTTP-to-HTTPS redirect:&lt;/p&gt;
&lt;p&gt;Redirect permanent / https://misp.example&lt;/p&gt;
&lt;p&gt;Apache’s Redirect directive appends any portion of the requested path that follows the matched prefix to the configured destination URL. Because the destination did not end with /, attacker-controlled path content was appended directly to the hostname rather than to its URL path.&lt;/p&gt;
&lt;p&gt;For example, a request resembling:&lt;/p&gt;
&lt;p&gt;http://misp.example/@attacker.example/&lt;/p&gt;
&lt;p&gt;could result in a redirect resembling:&lt;/p&gt;
&lt;p&gt;https://misp.example@attacker.example/&lt;/p&gt;
&lt;p&gt;Under standard URL parsing, misp.example is interpreted as user information and attacker.example as the destination host. An unauthenticated remote attacker could therefore construct a URL hosted under the legitimate MISP domain that redirects users to an attacker-controlled website.&lt;/p&gt;
&lt;p&gt;The vulnerability could be used for phishing, credential collection, or potentially disclosing sensitive query-string information preserved during the redirect. Exploitation requires a user to follow the crafted HTTP URL.&lt;/p&gt;
&lt;p&gt;The fix adds the missing trailing slash to the redirect destination, ensuring that appended request data remains part of the path on the configured MISP host.&lt;/p&gt;
&lt;p&gt;Existing installationsExisting MISP installations should review their Apache HTTP virtual-host configuration and ensure that the HTTPS redirect destination ends with a trailing slash:&lt;/p&gt;
&lt;p&gt;Redirect permanent / ht…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; misp&lt;/p&gt;
&lt;p&gt;MISP installation scripts generated an Apache HTTP virtual-host configuration containing an incorrectly formatted HTTP-to-HTTPS redirect:&lt;/p&gt;
&lt;p&gt;Redirect permanent / https://misp.example&lt;/p&gt;
&lt;p&gt;Apache’s Redirect directive appends any portion of the requested path that follows the matched prefix to the configured destination URL. Because the destination did not end with /, attacker-controlled path content was appended directly to the hostname rather than to its URL path.&lt;/p&gt;
&lt;p&gt;For example, a request resembling:&lt;/p&gt;
&lt;p&gt;http://misp.example/@attacker.example/&lt;/p&gt;
&lt;p&gt;could result in a redirect resembling:&lt;/p&gt;
&lt;p&gt;https://misp.example@attacker.example/&lt;/p&gt;
&lt;p&gt;Under standard URL parsing, misp.example is interpreted as user information and attacker.example as the destination host. An unauthenticated remote attacker could therefore construct a URL hosted under the legitimate MISP domain that redirects users to an attacker-controlled website.&lt;/p&gt;
&lt;p&gt;The vulnerability could be used for phishing, credential collection, or potentially disclosing sensitive query-string information preserved during the redirect. Exploitation requires a user to follow the crafted HTTP URL.&lt;/p&gt;
&lt;p&gt;The fix adds the missing trailing slash to the redirect destination, ensuring that appended request data remains part of the path on the configured MISP host.&lt;/p&gt;
&lt;p&gt;Existing installationsExisting MISP installations should review their Apache HTTP virtual-host configuration and ensure that the HTTPS redirect destination ends with a trailing slash:&lt;/p&gt;
&lt;p&gt;Redirect permanent / ht…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-67178</guid>
    </item>
  </channel>
</rss>
