iManager is a management portal for Novell's eDirectory server. More information about iManager is available at the link shown.
Remote exploitation of a DoS vulnerability in Novell Inc.'s iManager could allow attackers to crash the iManager Tomcat server.
The vulnerability specifically exists due to improper handling of a an HTTP POST request with a long TREE parameter. When such a request is received, a NULL pointer dereference occurs, leading to a crash of the service. iDefense Labs testing has indicated that any string longer than 256 bytes will be effective.
Exploitation requires that an attacker send a specially constructed HTTP request to the server. This crashes the server, making it unusable until it is restarted.
iDefense has confirmed this vulnerability in Novell iManager 2.5. All previous versions are suspected vulnerable.
iDefense is currently unaware of any workarounds for this issue.
Novell has addressed this vulnerability within iManager version 2.6. Upgrading to this version will alleviate exposure to the vulnerability.
The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2006-4517 to this issue. This is a candidate for inclusion in the CVE list (http://cve.mitre.org),which standardizes names for security problems.
08/17/2006 Initial vendor notification
08/18/2006 Initial vendor response
10/06/2006 Second vendor notification
10/31/2006 Coordinated public disclosure
This vulnerability was reported to iDefense by CIRT.DK.
Get paid for vulnerability research
Free tools, research and upcoming events
Copyright © 2006 Verisign, Inc.
Permission is granted for the redistribution of this alert electronically. It may not be edited in any way without the express written consent of iDefense. If you wish to reprint the whole or any part of this alert in any other medium other than electronically, please email firstname.lastname@example.org for permission.
Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.