[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fvt_FkJLIY-P78PhKZFrq_IoMgMOIKQhiAwN18Zr4zOM":3},{"success":4,"data":5},true,{"vendor":6,"topVulnerabilitiesByEpss":31,"kevVulnerabilities":92,"topProductsByCves":93,"seoMetadata":97,"meta":106},{"vendorId":7,"vendorName":8,"productCount":9,"cveCount":10,"kevCount":11,"versionCount":12,"lastCveUpdate":13,"firstLetter":14,"products":15,"description":30},13153,"haproxy",3,31,0,775,"2024-09-04","h",[16,20,25],{"id":17,"product_name":8,"version_count":18,"cve_count":19,"kev_count":11,"last_cve_update":13},53579,419,30,{"id":21,"product_name":22,"version_count":9,"cve_count":23,"kev_count":11,"last_cve_update":24},53580,"proxyprotocol",1,"2019-07-23",{"id":26,"product_name":27,"version_count":28,"cve_count":11,"kev_count":11,"last_cve_update":29},53578,"aloha",353,null,"Haproxy is a technology vendor with 3 tracked products and 31 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this vendor.",[32,40,47,52,57,62,67,72,77,85],{"cveId":33,"description":34,"publishedDate":24,"cvssScore":35,"cvssVersion":36,"severity":37,"isKev":38,"epssScore":39},"CVE-2019-14241","HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.",7.5,"v3.0","High",false,0.7024,{"cveId":41,"description":42,"publishedDate":43,"cvssScore":44,"cvssVersion":45,"severity":37,"isKev":38,"epssScore":46},"CVE-2020-11100","In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP\u002F2 request, possibly causing remote code execution.","2020-04-02",8.8,"v3.1",0.61593,{"cveId":48,"description":49,"publishedDate":50,"cvssScore":35,"cvssVersion":45,"severity":37,"isKev":38,"epssScore":51},"CVE-2021-40346","An integer overflow exists in HAProxy 2.0 through 2.5 in htx_add_header that can be exploited to perform an HTTP request smuggling attack, allowing an attacker to bypass all configured http-request HAProxy ACLs and possibly other ACLs.","2021-09-08",0.58832,{"cveId":53,"description":54,"publishedDate":55,"cvssScore":35,"cvssVersion":36,"severity":37,"isKev":38,"epssScore":56},"CVE-2016-5360","HAproxy 1.6.x before 1.6.6, when a deny comes from a reqdeny rule, allows remote attackers to cause a denial of service (uninitialized memory access and crash) or possibly have unspecified other impact via unknown vectors.","2016-06-30",0.4282,{"cveId":58,"description":59,"publishedDate":60,"cvssScore":35,"cvssVersion":45,"severity":37,"isKev":38,"epssScore":61},"CVE-2022-0711","A flaw was found in the way HAProxy processed HTTP responses containing the \"Set-Cookie2\" header. This flaw could allow an attacker to send crafted HTTP response packets which lead to an infinite loop, eventually resulting in a denial of service condition. The highest threat from this vulnerability is availability.","2022-03-02",0.16563,{"cveId":63,"description":64,"publishedDate":65,"cvssScore":35,"cvssVersion":45,"severity":37,"isKev":38,"epssScore":66},"CVE-2019-18277","A flaw was found in HAProxy before 2.0.6. In legacy mode, messages featuring a transfer-encoding header missing the \"chunked\" value were not being correctly rejected. The impact was limited but if combined with the \"http-reuse always\" setting, it could be used to help construct an HTTP request smuggling attack against a vulnerable component employing a lenient parser that would ignore the content-length header as soon as it saw a transfer-encoding one (even if not entirely valid according to the specification).","2019-10-23",0.10068,{"cveId":68,"description":69,"publishedDate":70,"cvssScore":35,"cvssVersion":36,"severity":37,"isKev":38,"epssScore":71},"CVE-2018-10184","An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the max_frame_size setting instead of being checked against the bufsize. The max_frame_size only applies to outgoing traffic and not to incoming, so if a large enough frame size is advertised in the SETTINGS frame, a wrapped frame will be defragmented into a temporary allocated buffer where the second fragment may overflow the heap by up to 16 kB. It is very unlikely that this can be exploited for code execution given that buffers are very short lived and their addresses not realistically predictable in production, but the likelihood of an immediate crash is absolutely certain.","2018-05-09",0.08302,{"cveId":73,"description":74,"publishedDate":75,"cvssScore":35,"cvssVersion":36,"severity":37,"isKev":38,"epssScore":76},"CVE-2018-20103","An issue was discovered in dns.c in HAProxy through 1.8.14. In the case of a compressed pointer, a crafted packet can trigger infinite recursion by making the pointer point to itself, or create a long chain of valid pointers resulting in stack exhaustion.","2018-12-12",0.06593,{"cveId":78,"description":79,"publishedDate":80,"cvssScore":81,"cvssVersion":82,"severity":83,"isKev":38,"epssScore":84},"CVE-2013-1912","Buffer overflow in HAProxy 1.4 through 1.4.22 and 1.5-dev through 1.5-dev17, when HTTP keep-alive is enabled, using HTTP keywords in TCP inspection rules, and running with rewrite rules that appends to requests, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted pipelined HTTP requests that prevent request realignment from occurring.","2013-04-10",5.1,"v2","Medium",0.05569,{"cveId":86,"description":87,"publishedDate":88,"cvssScore":89,"cvssVersion":45,"severity":90,"isKev":38,"epssScore":91},"CVE-2023-25725","HAProxy before 2.7.3 may allow a bypass of access control because HTTP\u002F1 headers are inadvertently lost in some situations, aka \"request smuggling.\" The HTTP header parsers in HAProxy may accept empty header field names, which could be used to truncate the list of HTTP headers and thus make some headers disappear after being parsed and processed for HTTP\u002F1.0 and HTTP\u002F1.1. For HTTP\u002F2 and HTTP\u002F3, the impact is limited because the headers disappear before being parsed and processed, as if they had not been sent by the client. The fixed versions are 2.7.3, 2.6.9, 2.5.12, 2.4.22, 2.2.29, and 2.0.31.","2023-02-14",9.1,"Critical",0.05448,[],[94,95,96],{"id":17,"product_name":8,"version_count":18,"cve_count":19,"kev_count":11,"last_cve_update":13},{"id":21,"product_name":22,"version_count":9,"cve_count":23,"kev_count":11,"last_cve_update":24},{"id":26,"product_name":27,"version_count":28,"cve_count":11,"kev_count":11,"last_cve_update":29},{"title":98,"metaDescription":99,"keywords":100,"structuredData":101},"Haproxy - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Haproxy covering 3 products with 31 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Haproxy vulnerabilities, Haproxy security, Haproxy CVE, Haproxy threat intelligence, vendor security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":102,"@type":103,"name":104,"description":99,"url":105},"https:\u002F\u002Fschema.org","Organization","Haproxy","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Fhaproxy",{"totalProducts":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":13,"generatedAt":107,"apiVersion":108},"2026-10-17T19:08:33.078Z","3.0"]