CVE-2009-2316 json
Multiple cross-site scripting (XSS) vulnerabilities in IBM Tivoli Identity Manager (ITIM) 5.0 allow remote attackers to inject arbitrary we…
published 2009-07-05 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2312
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in IBM Tivoli Identity Manager (ITIM) 5.0 allow remote attackers to inject arbitrary web script or HTML by entering an unspecified URL in (1) the self-service UI interface or (2) the console interface. NOTE: it was later reported that 4.6.0 is also affected by the first vector.
Patch / fix
Exploit prediction
1.71% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
www-01.ibm.com
/support/docview.wss?uid=swg24023640
patch, vendor-advisory
-
www-01.ibm.com
/support/docview.wss?uid=swg1IZ54310
vendor-advisory
-
www-01.ibm.com
/support/docview.wss?uid=swg1IZ55518
vendor-advisory
-
www-01.ibm.com
/support/docview.wss?uid=swg1IZ54311
vendor-advisory
-
secunia.com
/advisories/35696
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2009/2106
vdb-entry
-
securityfocus.com
/bid/35566
vdb-entry
- www-01.ibm.com /support/docview.wss?uid=swg24023929
-
secunia.com
/advisories/36119
third-party-advisory
-
osvdb.org
/55550
vdb-entry
-
securitytracker.com
/id?1022508
vdb-entry
-
vupen.com
/english/advisories/2009/1774
vdb-entry
-
osvdb.org
/55551
vdb-entry
Sources
- CVE List CVE-2009-2316
- NVD CVE-2009-2316
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.