# CVE-2004-2298: Hardcoded credentials in n/a

> Remote attackers can read and write mail data using default NMAP credentials in Novell NetMail unless administrators change them.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m9fj-g263-c8f3

## What is CVE-2004-2298?

CVE-2004-2298 is a medium-severity vulnerability in n/a, published on 5 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Novell Internet Messaging System (NIMS) 2.6 and 3.0, and NetMail 3.1 and 3.5, is installed with a default NMAP authentication credential, which allows remote attackers to read and write mail store data if the administrator does not change the credential by using the NMAP Credential Generator.

## Which versions are affected by CVE-2004-2298?

It affects 2 products.


Products: Novell Internet Messaging System, Novell Netmail.

## How do I fix CVE-2004-2298?

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

## Is CVE-2004-2298 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2298 and fix it if it is affected.

What it is: CVE-2004-2298 is a medium-severity vulnerability in n/a, published on 5 Aug 2005. 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-2004-2298 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-2004-2298/ (Markdown: https://insights.sbomify.com/CVE-2004-2298/index.md)
```

## Sources

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

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