CVE-2008-6520

CVE-2008-6520 is a critical-severity vulnerability in Imatix Xitami with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-134.

Key facts

Description

Multiple format string vulnerabilities in the SSI filter in Xitami Web Server 2.5c2, and possibly other versions, allow remote attackers to cause a denial of service (daemon crash) and possibly execute arbitrary code via format string specifiers in a URI that ends in (1) .ssi, (2) .shtm, or (3) .shtml, which triggers incorrect logging code involving the sendfmt function in the SMT kernel.

Frequently asked questions

What is CVE-2008-6520?
Multiple format string vulnerabilities in the SSI filter in Xitami Web Server 2.5c2, and possibly other versions, allow remote attackers to cause a denial of service (daemon crash) and possibly execute arbitrary code via format string specifiers in a URI that ends in (1) .ssi, (2) .shtm, or (3) .shtml, which triggers incorrect logging code involving the sendfmt function in the SMT kernel.
How severe is CVE-2008-6520?
CVE-2008-6520 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2008-6520 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-6520?
CVE-2008-6520 affects Imatix Xitami. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2008-6520?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2008-6520 published?
CVE-2008-6520 was published on 2009-03-25 and last updated on 2026-06-16.

References

Affected products (1)

More vulnerabilities in Imatix Xitami

All CVEs affecting Imatix Xitami →

Other CWE-134 vulnerabilities

Browse all CWE-134 vulnerabilities →