CVE-2004-2026
Summary
| CVE | CVE-2004-2026 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2004-12-31 05:00:00 UTC |
| Updated | 2025-04-03 01:03:51 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v2.0 7.5 from [email protected]
AV:N/AC:L/Au:N/C:P/I:P/A:P
Problem Types: NVD-CWE-Other | n/a
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
LowAuthentication
NoneConfidentiality
PartialIntegrity
PartialAvailability
PartialAV:N/AC:L/Au:N/C:P/I:P/A:P
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| archives.neohapsis.com/archives/fulldisclosure/2004-05/0343.html | af854a3a-2127-422b-91ae-364da2661108 | archives.neohapsis.com | Exploit |
| ANNOUNCE: Pound - reverse proxy and load balancer - v1.6 / Robert Segall | af854a3a-2127-422b-91ae-364da2661108 | www.apsis.ch | |
| APSIS Pound Remote Format String Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | Exploit, Patch |
| Secunia - Advisories - Pound "logmsg()" Format String Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | secunia.com | Patch |
| www.osvdb.org/5746 | af854a3a-2127-422b-91ae-364da2661108 | www.osvdb.org | |
| Gentoo Linux Documentation -- Pound format string vulnerability | af854a3a-2127-422b-91ae-364da2661108 | security.gentoo.org | Patch |
| Pound Format String Flaw in Syslog Processing Lets Remote Users Execute Arbitrary Code - SecurityTracker | af854a3a-2127-422b-91ae-364da2661108 | securitytracker.com | |
| IBM X-Force Exchange | af854a3a-2127-422b-91ae-364da2661108 | exchange.xforce.ibmcloud.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.