# CVE-2005-0322: Weak cryptography in n/a

> Local attackers can extract passwords from configuration files due to weak encryption in MERAK and Icewarp mail servers.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-98vg-cwwq-ccc6

## What is CVE-2005-0322?

CVE-2005-0322 is a high-severity vulnerability in n/a, published on 10 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MERAK Mail Server 7.6.0 with Icewarp Web Mail 5.3.0 and Mail Server 7.6.4r with Icewarp Mail Server 5.3.2 uses weak encryption in the (1) users.cfg, (2) settings.cfg, (3) users.dat or (4) user.dat files, which allows local users to extract the passwords.

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

It affects 2 products.


Products: Icewarp Web Mail, Merak Mail Server.

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

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

## Is CVE-2005-0322 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1670](https://insights.sbomify.com/CVE-2004-1670/): Path traversal in n/a (high 7.5)
- [CVE-2004-1672](https://insights.sbomify.com/CVE-2004-1672/): Missing authorization in n/a (high 7.5)
- [CVE-2004-1673](https://insights.sbomify.com/CVE-2004-1673/): File upload in n/a (high 7.5)
- [CVE-2004-1674](https://insights.sbomify.com/CVE-2004-1674/): Path traversal in n/a (high 7.5)
- [CVE-2002-0258](https://insights.sbomify.com/CVE-2002-0258/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0322 is a high-severity vulnerability in n/a, published on 10 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0322 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-2005-0322/ (Markdown: https://insights.sbomify.com/CVE-2005-0322/index.md)
```

## Sources

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

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