CVE-2009-0632 json
The IP Phone Personal Address Book (PAB) Synchronizer feature in Cisco Unified Communications Manager (aka CUCM, formerly CallManager) 4.1,…
published 2009-03-12 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0635
- cvss
- 9.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
The IP Phone Personal Address Book (PAB) Synchronizer feature in Cisco Unified Communications Manager (aka CUCM, formerly CallManager) 4.1, 4.2 before 4.2(3)SR4b, 4.3 before 4.3(2)SR1b, 5.x before 5.1(3e), 6.x before 6.1(3), and 7.0 before 7.0(2) sends privileged directory-service account credentials to the client in cleartext, which allows remote attackers to modify the CUCM configuration and perform other privileged actions by intercepting these credentials, and then using them in requests unrelated to the intended synchronization task, as demonstrated by (1) DC Directory account credentials in CUCM 4.x and (2) TabSyncSysUser account credentials in CUCM 5.x through 7.x.
Patch / fix
Exploit prediction
3.02% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
cisco.com
/en/US/products/products_security_advisory09186a0080a8643c.shtml
vendor-advisory, patch
-
vupen.com
/english/advisories/2009/0675
vdb-entry, patch, vendor-advisory
-
cisco.com
/en/US/products/products_applied_mitigation_bulletin09186a0080a86434.html
vendor-advisory
-
securityfocus.com
/bid/34082
vdb-entry
-
osvdb.org
/52589
vdb-entry
-
securitytracker.com
/id?1021839
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49196
vdb-entry
-
secunia.com
/advisories/34238
third-party-advisory
Sources
- CVE List CVE-2009-0632
- NVD CVE-2009-0632
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.