# CVE-2005-3189: Path traversal in n/a

> Remote attackers can read arbitrary email messages via directory traversal in the SELECT command of Qualcomm WorldMail IMAP Server.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2c75-m9vm-4fvh

## What is CVE-2005-3189?

CVE-2005-3189 is a medium-severity path traversal vulnerability in n/a, published on 18 Nov 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in Qualcomm WorldMail IMAP Server allows remote attackers to read arbitrary email messages via ".." sequences in the SELECT command.

## Which versions are affected by CVE-2005-3189?

It affects 1 product.


Products: Qualcomm Worldmail Imap Server.

## How do I fix CVE-2005-3189?

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

## Is CVE-2005-3189 being exploited?

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

Public exploit code:

- Qualcomm WorldMail Server 3.0 - Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3189 and fix it if it is affected.

What it is: CVE-2005-3189 is a medium-severity path traversal vulnerability in n/a, published on 18 Nov 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3189 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-2005-3189/ (Markdown: https://insights.sbomify.com/CVE-2005-3189/index.md)
```

## Sources

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

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