CVE-2004-0536 json
Format string vulnerability in Tripwire commercial 4.0.1 and earlier, including 2.4, and open source 2.3.1 and earlier, allows local users…
published 2004-06-08 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0535
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
Format string vulnerability in Tripwire commercial 4.0.1 and earlier, including 2.4, and open source 2.3.1 and earlier, allows local users to gain privileges via format string specifiers in a file name, which is used in the generation of an email report.
Patch / fix
- tripwire Debian 14, Debian 13, Debian 12 2.3.1.2.0-2.1
debian advisories DEBIAN-CVE-2004-0536
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2004-0536 updated
security flaw
-
Red Hat Enterprise Linux ES version 2.1 Red Hat Enterprise Linux WS version 2.1fixed: vendor fix RHSA-2004:244
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
redhat.com
/support/errata/RHSA-2004-244.html
vendor-advisory
-
security.gentoo.org
/glsa/glsa-200406-02.xml
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/16309
vdb-entry
-
marc.info
/?l=bugtraq&m=108630983009228&w=2
mailing-list
-
marc.info
/?l=bugtraq&m=108627481507249&w=2
mailing-list
-
securityfocus.com
/bid/10454
vdb-entry
Sources
- CVE List CVE-2004-0536
- NVD CVE-2004-0536
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.