# CVE-2006-4517: Null dereference in n/a

> Remote attackers can crash the Tomcat server in Novell iManager by sending a long TREE parameter in an HTTP POST request.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h747-m9jw-xj3m

## What is CVE-2006-4517?

CVE-2006-4517 is a high-severity vulnerability in n/a, published on 1 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Novell iManager 2.5 and 2.0.2 allows remote attackers to cause a denial of service (crash) in the Tomcat server via a long TREE parameter in an HTTP POST, which triggers a NULL pointer dereference.

Weakness: CWE-399, CWE-189

## Which versions are affected by CVE-2006-4517?

It affects 1 product.


Products: Novell Imanager.

## How do I fix CVE-2006-4517?

No fix has been published for CVE-2006-4517 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-4517 being exploited?

There is no known exploitation of CVE-2006-4517 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-3268](https://insights.sbomify.com/CVE-2013-3268/): Auth bypass in n/a (critical 10.0)
- [CVE-2005-1730](https://insights.sbomify.com/CVE-2005-1730/): Null dereference in n/a (critical 9.3)
- [CVE-2010-1929](https://insights.sbomify.com/CVE-2010-1929/): Memory corruption in n/a (critical 9.0)
- [CVE-2009-4486](https://insights.sbomify.com/CVE-2009-4486/): Memory corruption in n/a (high 7.5)
- [CVE-2008-3488](https://insights.sbomify.com/CVE-2008-3488/): Unspecified vulnerability in Novell iManager before 2.7 SP1 (2.7.1) allows remote attackers to delete Plug-in Studio created Property Book P (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4517 and fix it if it is affected.

What it is: CVE-2006-4517 is a high-severity vulnerability in n/a, published on 1 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4517 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-4517/ (Markdown: https://insights.sbomify.com/CVE-2006-4517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-4517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-4517
- OSV: https://osv.dev/vulnerability/CVE-2006-4517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-4517/
Summaries are generated and may contain mistakes; the official description above is the record.