CVE-2009-3699

CVE-2009-3699 is a critical-severity vulnerability in Ibm Vios with a CVSS 2.0 base score of 10.0. Its EPSS exploit-prediction score of 62% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-119.

Key facts

Description

Stack-based buffer overflow in libcsa.a (aka the calendar daemon library) in IBM AIX 5.x through 5.3.10 and 6.x through 6.1.3, and VIOS 2.1 and earlier, allows remote attackers to execute arbitrary code via a long XDR string in the first argument to procedure 21 of rpc.cmsd.

Frequently asked questions

What is CVE-2009-3699?
Stack-based buffer overflow in libcsa.a (aka the calendar daemon library) in IBM AIX 5.x through 5.3.10 and 6.x through 6.1.3, and VIOS 2.1 and earlier, allows remote attackers to execute arbitrary code via a long XDR string in the first argument to procedure 21 of rpc.cmsd.
How severe is CVE-2009-3699?
CVE-2009-3699 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2009-3699 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 62% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-3699?
CVE-2009-3699 primarily affects Ibm Vios. In total, 31 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-3699?
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-2009-3699 published?
CVE-2009-3699 was published on 2009-10-15 and last updated on 2026-06-16.

References

Affected products (31)

More vulnerabilities in Ibm Vios

All CVEs affecting Ibm Vios →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →