<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 08:32:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-23452 — Apache bRPC: HTTP request smuggling vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-23452</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache bRPC&lt;/p&gt;
&lt;p&gt;Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request.&lt;/p&gt;
&lt;p&gt;Vulnerability Cause Description：&lt;/p&gt;
&lt;p&gt;The http_parser does not comply with the RFC-7230 HTTP 1.1 specification.&lt;/p&gt;
&lt;p&gt;Attack scenario:
If a message is received with both a Transfer-Encoding and a Content-Length header field, such a message might indicate an attempt to perform request smuggling or response splitting.
One particular attack scenario is that a bRPC made http server on the backend receiving requests in one persistent connection from frontend server that uses TE to parse request with the logic that &amp;#39;chunk&amp;#39; is contained in the TE field. in that case an attacker can smuggle a request into the connection to the backend server.&lt;/p&gt;
&lt;p&gt;Solution:
You can choose one solution from below:
1. Upgrade bRPC to version 1.8.0, which fixes this issue. Download link:  https://github.com/apache/brpc/releases/tag/1.8.0
 2. Apply this patch:  https://github.com/apache/brpc/pull/2518&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache bRPC&lt;/p&gt;
&lt;p&gt;Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request.&lt;/p&gt;
&lt;p&gt;Vulnerability Cause Description：&lt;/p&gt;
&lt;p&gt;The http_parser does not comply with the RFC-7230 HTTP 1.1 specification.&lt;/p&gt;
&lt;p&gt;Attack scenario:
If a message is received with both a Transfer-Encoding and a Content-Length header field, such a message might indicate an attempt to perform request smuggling or response splitting.
One particular attack scenario is that a bRPC made http server on the backend receiving requests in one persistent connection from frontend server that uses TE to parse request with the logic that &amp;#39;chunk&amp;#39; is contained in the TE field. in that case an attacker can smuggle a request into the connection to the backend server.&lt;/p&gt;
&lt;p&gt;Solution:
You can choose one solution from below:
1. Upgrade bRPC to version 1.8.0, which fixes this issue. Download link:  https://github.com/apache/brpc/releases/tag/1.8.0
 2. Apply this patch:  https://github.com/apache/brpc/pull/2518&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-23452</guid>
    </item>
  </channel>
</rss>
