Skip to content
Fencer Vulns
low 1.9

CVE-2008-4579 json

The (1) fence_apc and (2) fence_apc_snmp programs, as used in (a) fence 2.02.00-r1 and possibly (b) cman, when running in verbose mode, all…

published 2008-10-15 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4559

cvss
1.9
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 29%
public exploits
0
none known

Summary

The (1) fence_apc and (2) fence_apc_snmp programs, as used in (a) fence 2.02.00-r1 and possibly (b) cman, when running in verbose mode, allows local users to append to arbitrary files via a symlink attack on the apclog temporary file.

Patch / fix

  • fence RHEL 4 CLUSTER 1.32.68-5.el4
  • cman RHEL 5 2.0.115-1.el5

red hat advisories RHSA-2011:0266RHSA-2009:1341

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-2008-4579 updated cvss 1.5

cman/fence: insecure temporary file usage in the apc fence agents

  • Red Hat Cluster Suite 4AS fence 1.32.68-5.el4 Red Hat Cluster Suite 4ES fence 1.32.68-5.el4 Red Hat Cluster Suite 4WS fence 1.32.68-5.el4
    fixed: vendor fix RHSA-2011:0266
  • Red Hat Enterprise Linux (v. 5 server) cman 2.0.115-1.el5 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) cman 2.0.115-1.el5
    fixed: vendor fix RHSA-2009:1341

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.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

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.