# CVE-2006-0173: Other in n/a

> Remote attackers can misrepresent file types and names to trick users into downloading dangerous content in Hummingbird Collaboration.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j264-3w7c-r6mm

## What is CVE-2006-0173?

CVE-2006-0173 is a medium-severity vulnerability in n/a, published on 11 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Hummingbird Collaboration (aka Hummingbird Enterprise Collaboration) 5.21 and earlier allows remote attackers to misrepresent the type and name of a file via modified doc_ext and id parameters, which might trick a user into downloading dangerous or unexpected content.

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

It affects 1 product.


Products: Hummingbird Enterprise Collaboration.

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

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

## Is CVE-2006-0173 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0173 exists.

Public exploit code:

- Hummingbird Collaboration - Crafted URL File Property Obscuration Download (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-0172](https://insights.sbomify.com/CVE-2006-0172/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0173 is a medium-severity vulnerability in n/a, published on 11 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0173 exists.

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-0173/ (Markdown: https://insights.sbomify.com/CVE-2006-0173/index.md)
```

## Sources

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

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