{"id":3052,"date":"2025-04-04T10:03:35","date_gmt":"2025-04-04T10:03:35","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2025\/04\/04\/apache-traffic-server-vulnerability-let-attackers-smuggle-requests\/"},"modified":"2025-04-04T10:03:35","modified_gmt":"2025-04-04T10:03:35","slug":"apache-traffic-server-vulnerability-let-attackers-smuggle-requests","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2025\/04\/04\/apache-traffic-server-vulnerability-let-attackers-smuggle-requests\/","title":{"rendered":"Apache Traffic Server Vulnerability Let Attackers Smuggle Requests"},"content":{"rendered":"<p>    Apache Traffic Server Vulnerability Let Attackers Smuggle Requests<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p>A critical security vulnerability in <a href=\"https:\/\/cybersecuritynews.com\/apache-traffic-server-vulnerabilities\/\" target=\"_blank\" rel=\"noreferrer noopener\">Apache Traffic Server (ATS)<\/a> has been discovered. By exploiting how the server processes chunked messages, attackers can perform request smuggling attacks.\u00a0<\/p>\n<p>The vulnerability, tracked as CVE-2024-53868, affects multiple versions of this high-performance HTTP proxy server and requires system administrators\u2019 immediate attention.<\/p>\n<p>According to the advisory, the vulnerability stems from a flaw in how Apache Traffic Server handles HTTP chunked transfer encoding\u2014a method that allows data to be sent in a series of chunks rather than all at once.\u00a0<\/p>\n<p>When processing malformed chunked messages, ATS fails to properly validate the message format, creating a security gap that malicious actors can exploit.<\/p>\n<p>Specifically, the issue involves how ATS handles malformed chunked message bodies. Based on findings from related <a href=\"https:\/\/cybersecuritynews.com\/39m-secret-api-keys-credentials-leaked-from-github\/\" target=\"_blank\" rel=\"noreferrer noopener\">GitHub<\/a> issues, ATS improperly accepts and forwards requests containing invalid formatting elements, such as carriage returns within chunk-ext whitespace, where only spaces and tabs should be permitted.<\/p>\n<h2 class=\"wp-block-heading\"><strong>Apache Traffic Server Vulnerability<\/strong><\/h2>\n<p>Additionally, ATS accepts bare Line Feed (LF) characters as line endings within chunked message bodies instead of requiring the standard Carriage Return + Line Feed (CRLF) sequence.<\/p>\n<p>For example, when a specially crafted HTTP request using the Transfer-Encoding: chunked header with intentionally malformed chunk formatting is sent to an ATS server, the server processes it in a way that differs from how backend servers might interpret the same request.\u00a0<\/p>\n<p>This inconsistency creates the opportunity for request smuggling.<\/p>\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter\"><img decoding=\"async\" src=\"https:\/\/lh7-rt.googleusercontent.com\/docsz\/AD_4nXfPDDvmijtp0CWw_-9-NuF3l0v_dtZxIbDA5_z2woSipEIJZZopjLyGW5nnCl99x24A5O2g5sIFdqflXJfD8RxAGGKIm4aysDEo0TDT74LD5nE57Terlx5v0JrwYzLg_J1afrkEnA?key=5Op9TrRT1fX175I8ziHhKzDi\" alt=\"\"><\/figure>\n<\/div>\n<p>The above-simplified example demonstrates how an improper line ending (bare LF represented as n) in a chunked message might be accepted by ATS and forwarded to backend servers without proper normalization.<\/p>\n<p>The summary of the vulnerability is given below:<\/p>\n<figure class=\"wp-block-table is-style-stripes\">\n<table class=\"has-fixed-layout\">\n<tbody>\n<tr>\n<td><strong>Risk Factors<\/strong><\/td>\n<td><strong>Details<\/strong><\/td>\n<\/tr>\n<tr>\n<td>\n<br \/>Affected Products<\/td>\n<td>Apache Traffic Server (ATS) versions 9.2.0 to 9.2.9 and 10.0.0 to 10.0.4<\/td>\n<\/tr>\n<tr>\n<td>\n<br \/>Impact<\/td>\n<td>Cache poisoning, Bypassing security controls, and Session hijacking<\/td>\n<\/tr>\n<tr>\n<td>\n<br \/>Exploit Prerequisites<\/td>\n<td>A specially crafted HTTP request using chunked transfer encoding<\/td>\n<\/tr>\n<tr>\n<td>CVSS 3.1 Score<\/td>\n<td>6.5 (Medium)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<h2 class=\"wp-block-heading\"><strong>Security Implications<\/strong><\/h2>\n<p>This request smuggling vulnerability poses several serious risks:<\/p>\n<ul class=\"wp-block-list\">\n<li>\n<strong>Bypassing security controls:<\/strong> Attackers might circumvent web application firewalls or access control lists designed to protect backend servers.<\/li>\n<li>\n<strong>Cache poisoning:<\/strong> By manipulating how requests are interpreted, attackers could poison the server cache, affecting responses sent to legitimate users.<\/li>\n<li>\n<strong>Session hijacking:<\/strong> In certain scenarios, attackers might intercept or manipulate user sessions, potentially gaining unauthorized access to sensitive accounts.<\/li>\n<li>\n<strong>Data exposure:<\/strong> The vulnerability could lead to exposure of sensitive information due to inconsistent request handling.<\/li>\n<\/ul>\n<p>The vulnerability has been assigned a CVSS base score of 6.5, indicating a medium severity level.<\/p>\n<p>The following Apache Traffic Server versions are vulnerable to CVE-2024-53868:<\/p>\n<ul class=\"wp-block-list\">\n<li>ATS 9.0.0 through 9.2.9<\/li>\n<li>ATS 10.0.0 through 10.0.4<\/li>\n<\/ul>\n<h2 class=\"wp-block-heading\"><strong>Mitigation Steps<\/strong><\/h2>\n<p>Organizations using Apache Traffic Server should implement the following mitigation measures immediately:<\/p>\n<p>Upgrade to patched versions:<\/p>\n<ul class=\"wp-block-list\">\n<li>For 9.x branch users: Upgrade to version 9.2.10 or later<\/li>\n<li>For 10.x branch users: Upgrade to version 10.0.5 or later<\/li>\n<li>Review and restrict network access to Apache Traffic Server instances<\/li>\n<li>Monitor traffic for unusual HTTP request patterns<\/li>\n<li>Implement additional network-level security controls<\/li>\n<li>Conduct thorough security assessments of existing deployments<\/li>\n<\/ul>\n<p>The Apache Software Foundation <a href=\"https:\/\/lists.apache.org\/thread\/rwyx91rsrnmpjbm04footfjjf6m9d1c9\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">released<\/a> these security updates on April 2, 2025, with commits addressing the vulnerability now available in the project\u2019s repository.<\/p>\n<p>Given the widespread use of Apache Traffic Server in <a href=\"https:\/\/cybersecuritynews.com\/best-5-multi-cdn-tools\/\" target=\"_blank\" rel=\"noreferrer noopener\">content delivery networks (CDNs)<\/a> and high-traffic websites, administrators are urged to prioritize these updates to protect their infrastructure from potential exploitation.<\/p>\n<p class=\"has-text-align-center has-background\" style=\"background:linear-gradient(180deg,rgb(238,238,238) 92%,rgb(169,184,195) 100%)\"><strong><code><strong><code>Investigate Real-World Malicious Links &amp; Phishing Attacks With\u00a0<strong>Threat Intelligence Lookup<\/strong>\u00a0-\u00a0<a href=\"https:\/\/intelligence.any.run\/plans?utm_source=csn&amp;utm_medium=article&amp;utm_campaign=3-techniques-to-improve-th&amp;utm_content=plans&amp;utm_term=010425\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Try 50 Request for Free<\/a><\/code><\/strong><\/code><\/strong><\/p>\n<p>The post <a href=\"https:\/\/cybersecuritynews.com\/apache-traffic-server-vulnerability\/\">Apache Traffic Server Vulnerability Let Attackers Smuggle Requests<\/a> appeared first on <a href=\"https:\/\/cybersecuritynews.com\/\">Cyber Security News<\/a>.<\/p>\n<\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><br \/>\n    Guru Baran<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/cybersecuritynews.com\/apache-traffic-server-vulnerability\/\">Go to cyber-security-news<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Apache Traffic Server Vulnerability Let Attackers Smuggle Requests A critical security vulnerability in Apache Traffic Server (ATS) has been discovered. By exploiting how the server processes chunked messages, attackers can perform request smuggling attacks.\u00a0 The vulnerability, tracked as CVE-2024-53868, affects multiple versions of this high-performance HTTP proxy server and requires system administrators\u2019 immediate attention. According [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[803,129,63,131],"tags":[130],"class_list":["post-3052","post","type-post","status-publish","format-standard","hentry","category-apache","category-cyber-security","category-cyber-security-news","category-vulnerability","tag-cyber-security-news"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/3052"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=3052"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/3052\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=3052"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=3052"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=3052"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}