apsis pound vulnerabilities

Latest apsis pound CVEs

Newest publication first

1. CVE-2018-21245 Pound before 2.8 allows HTTP request smuggling, a related issue to CVE-2016-10711.

   Published 2020-06-15

   Critical·CVSS 9.1 EPSS 1.1%

   Pound before 2.8 allows HTTP request smuggling, a related issue to CVE-2016-10711.

2. CVE-2016-10711 Apsis Pound before 2.8a allows request smuggling via crafted headers, a different vulnerability than CVE-2005-3751.

   Published 2018-01-29

   Critical·CVSS 9.8 EPSS 2.8%

   Apsis Pound before 2.8a allows request smuggling via crafted headers, a different vulnerability than CVE-2005-3751.

3. CVE-2005-3751 HTTP request smuggling vulnerability in Pound before 1.9.4 allows remote attackers to poison web caches, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with co...

   Published 2005-11-22

   Medium·CVSS 4.3 EPSS 1.5%

   HTTP request smuggling vulnerability in Pound before 1.9.4 allows remote attackers to poison web caches, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with conflicting Content-length and Transfer-encoding headers.

4. CVE-2004-2026 Format string vulnerability in the logmsg function in svc.c for Pound 1.5 and earlier allows remote attackers to execute arbitrary code via format string specifiers in syslog messages.

   Published 2005-05-10

   High·CVSS 7.5 EPSS 6.6%

   Format string vulnerability in the logmsg function in svc.c for Pound 1.5 and earlier allows remote attackers to execute arbitrary code via format string specifiers in syslog messages.

5. CVE-2005-1391 Buffer overflow in the add_port function in APSIS Pound 1.8.2 and earlier allows remote attackers to execute arbitrary code via a long Host HTTP header.

   Published 2005-05-02

   High·CVSS 7.5 EPSS 6.1%

   Buffer overflow in the add_port function in APSIS Pound 1.8.2 and earlier allows remote attackers to execute arbitrary code via a long Host HTTP header.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.