1856 matches found
CVE-2012-0256
Apache Traffic Server 2.0.x and 3.0.x before 3.0.4 and 3.1.x before 3.1.3 does not properly allocate heap memory, which allows remote attackers to cause a denial of service daemon crash via a long HTTP Host header...
Apache Traffic Server DoS
Server crash on oversized Host: header...
Apache Traffic Server HTTP主机标头处理缓冲区溢出漏洞
BUGTRAQ ID: 52696 CVE ID: CVE-2012-0256 Apache Traffic Server(ATS或TS)是一个高性能的、可扩展的模块化HTTP/1.1缓存代理服务器。 Apache Traffic Server在HTTP协议的实现上存在堆溢出漏洞,通过发送特制的HTTP消息到受影响服务器可造成拒绝访问或执行任意代码。 0 Apache Group Traffic Server 厂商补丁: Apache Group ------------ 目前厂商已经发布了升级补丁以修复这个安全问题,请到厂商的主页下载: http://httpd.apache.org/...
[ANNOUNCE] Apache Traffic Server releases for security incident CVE-2012-0256
Everyone, Below is our announcement for the security issue reported to us from Codenomicon, via CERT-FI. All previous versions of Apache Traffic Server are vulnerable, and we urge users to upgrade to either v3.0.4 or v3.1.3 immediately. Both releases are available from our download site at...
FreeBSD : Apache Traffic Server -- heap overflow vulnerability (acab2f88-7490-11e1-865f-00e0814cab4e)
CERT-FI reports : A heap overflow vulnerability has been found in the HTTP Hypertext Transfer Protocol protocol handling of Apache Traffic Server. The vulnerability allows an attacker to cause a denial of service or potentially to execute his own code by sending a specially modified HTTP message ...
CVE-2012-0256: Improper Restriction of Operations within the Bounds of a Memory Buffer
Apache Traffic Server 2.0.x and 3.0.x before 3.0.4 and 3.1.x before 3.1.3 does not properly allocate heap memory, which allows remote attackers to cause a denial of service daemon crash via a long HTTP Host header...
Apache Traffic Server -- heap overflow vulnerability
CERT-FI reports: A heap overflow vulnerability has been found in the HTTP Hypertext Transfer Protocol protocol handling of Apache Traffic Server. The vulnerability allows an attacker to cause a denial of service or potentially to execute his own code by sending a specially modified HTTP message t...
PT-2021-8119
Name of the Vulnerable Software and Affected Versions Puma versions prior to 5.5.1 and 4.3.9 Description The issue is related to HTTP request smuggling when using Puma with a proxy that forwards HTTP header values containing the LF character. This could allow a client to smuggle a request through...
CVE-2010-2952
Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source ports and transaction IDs, and does not properly use DNS query fields to validate responses, which makes it easier for man-in-the-middle attackers to poison the internal DNS cache via a crafte...
Design/Logic Flaw
Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source ports and transaction IDs, and does not properly use DNS query fields to validate responses, which makes it easier for man-in-the-middle attackers to poison the internal DNS cache via a crafte...
CVE-2010-2952
Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source ports and transaction IDs, and does not properly use DNS query fields to validate responses, which makes it easier for man-in-the-middle attackers to poison the internal DNS cache via a crafte...
CVE-2010-2952
Apache Traffic Server vulnerable in versions before 2.0.1 and in 2.1.x before 2.1.2-unstable. The issue stems from improper DNS source port/transaction ID handling and DNS query field validation, enabling MITM-style cache poisoning via crafted responses. Remediation: upgrade to Apache Traffic Ser...
CVE-2010-2952
Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source ports and transaction IDs, and does not properly use DNS query fields to validate responses, which makes it easier for man-in-the-middle attackers to poison the internal DNS cache via a crafte...
CVE-2010-2952: Improper Input Validation
Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source ports and transaction IDs, and does not properly use DNS query fields to validate responses, which makes it easier for man-in-the-middle attackers to poison the internal DNS cache via a crafte...
Apache Traffic Server Remote DNS Cache Poisoning Vulnerability
Apache Traffic Server is prone to a remote DNS cache-poisoning vulnerability. SPDX-FileCopyrightText: 2010 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only CPE =...
Apache Traffic Server (ATS) Detection (HTTP)
HTTP based detection of Apache Traffic Server ATS. SPDX-FileCopyrightText: 2010 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only ifdescription...
Apache Traffic Server Remote DNS Cache Poisoning Vulnerability
Apache Traffic Server is prone to a remote DNS cache-poisoning vulnerability. An attacker can exploit this issue to divert data from a legitimate site to an attacker-specified site. Successful exploits will allow the attacker to manipulate cache data, potentially facilitating man-in-the-middle,...
Knox Arkeia Server Backup 5.3.x Remote Root Exploit
Exploit for multiple platform in category remote exploits =================================================== Knox Arkeia Server Backup 5.3.x Remote Root Exploit =================================================== / Knox Arkiea Server Backup arkiead local/remote root exploit Targets for Redhat...
CVE-2003-0292
Cross-site scripting XSS vulnerability in Inktomi Traffic-Server 5.5.1 allows remote attackers to insert arbitrary web script or HTML into an error page that appears to come from the domain that the client is visiting, aka "Man-in-the-Middle" XSS...
CVE-2003-0292
Cross-site scripting XSS vulnerability in Inktomi Traffic-Server 5.5.1 allows remote attackers to insert arbitrary web script or HTML into an error page that appears to come from the domain that the client is visiting, aka "Man-in-the-Middle" XSS...