CWE
200
Advisory Published
Updated

CVE-2006-6637: Infoleak

First published: Tue Dec 19 2006(Updated: )

The Servlet Engine and Web Container in IBM WebSphere Application Server (WAS) before 6.0.2.17, when ibm-web-ext.xmi sets fileServingEnabled to true and servlet caching is enabled, allows remote attackers to obtain JSP source code and other sensitive information via "specific requests."

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
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.5
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.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.15
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.3
=6.0.2.1
=6.0.2.3
=6.0.2.5
=6.0.2.7
=6.0.2.9
=6.0.2.11
=6.0.2.13
=6.0.2.15

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What are the risks associated with CVE-2006-6637?

    CVE-2006-6637 allows remote attackers to access JSP source code and sensitive information, posing significant security risks to affected applications.

  • How can organizations mitigate CVE-2006-6637?

    Organizations can mitigate CVE-2006-6637 by disabling servlet caching and ensuring that file serving is not enabled in the ibm-web-ext.xmi configuration.

  • Which versions of IBM WebSphere Application Server are vulnerable to CVE-2006-6637?

    IBM WebSphere Application Server versions 6.0.2.1, 6.0.2.3, 6.0.2.5, 6.0.2.7, 6.0.2.9, 6.0.2.11, 6.0.2.13, and 6.0.2.15 are all vulnerable to CVE-2006-6637.

  • What actions should be taken if CVE-2006-6637 is detected in an environment?

    If CVE-2006-6637 is detected, it is crucial to immediately disable vulnerable configurations and apply appropriate patches or updates.

  • Is CVE-2006-6637 commonly exploited in the wild?

    While CVE-2006-6637 is a known vulnerability, its active exploitation may vary, so monitoring and patching are advised to prevent potential attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203