First published: Sun Oct 30 2011(Updated: )
The Java Naming and Directory Interface (JNDI) implementation in IBM WebSphere Application Server (WAS) 6.0 before 6.0.2.39, 6.1 before 6.1.0.29, and 7.0 before 7.0.0.7 does not properly restrict access to UserRegistry object methods, which allows remote attackers to obtain sensitive information via a crafted method call.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
IBM WebSphere Application Server Feature Pack for Web Services | =6.0 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.0.1 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.0.2 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.0.3 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.1 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.2 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.3 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.5 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.7 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.9 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.11 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.13 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.15 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.1.17 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.1 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.2 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.3 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.4 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.5 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.6 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.7 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.9 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.11 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.13 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.15 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.17 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.19 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.22 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.23 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.24 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.25 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.27 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.28 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.29 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.30 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.31 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.32 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.33 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.35 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.0.2.37 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.0 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.1 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.2 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.5 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.7 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.9 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.11 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.12 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.15 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.17 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.19 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.21 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.23 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.25 | |
IBM WebSphere Application Server Feature Pack for Web Services | =6.1.0.27 | |
IBM WebSphere Application Server Feature Pack for Web Services | =7.0 | |
IBM WebSphere Application Server Feature Pack for Web Services | =7.0.0.1 | |
IBM WebSphere Application Server Feature Pack for Web Services | =7.0.0.2 | |
IBM WebSphere Application Server Feature Pack for Web Services | =7.0.0.3 | |
IBM WebSphere Application Server Feature Pack for Web Services | =7.0.0.4 | |
IBM WebSphere Application Server Feature Pack for Web Services | =7.0.0.5 | |
IBM WebSphere Application Server Feature Pack for Web Services | =7.0.0.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-2747 is classified as a moderate severity vulnerability due to improper access restrictions in IBM WebSphere Application Server.
To mitigate CVE-2009-2747, users should upgrade to IBM WebSphere Application Server versions 6.0.2.39 or later, 6.1.0.29 or later, or 7.0.0.7 or later.
CVE-2009-2747 affects multiple versions of IBM WebSphere Application Server, specifically versions up to 6.0.2.38, 6.1.0.28, and 7.0.0.6.
CVE-2009-2747 can be exploited by remote attackers to gain unauthorized access to sensitive information through UserRegistry object methods.
While upgrading is the primary solution for CVE-2009-2747, temporarily restricting access to UserRegistry methods may provide limited mitigation.