# CVE-2004-2722: Information disclosure in n/a

> Local attackers can read plaintext passwords from Nessus configuration files, exposing sensitive credentials.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 6 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3v3x-cm3g-974v

## What is CVE-2004-2722?

CVE-2004-2722 is a low-severity vulnerability in n/a, published on 6 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Nessus 2.0.10a stores account passwords in plaintext in .nessusrc files, which allows local users to obtain passwords.  NOTE: the original researcher reports that the vendor has disputed this issue

Weakness: CWE-255

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

It affects 1 product.


Products: Nessus Nessus.

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

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

## Is CVE-2004-2722 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0374](https://insights.sbomify.com/CVE-2003-0374/): Multiple unknown vulnerabilities in Nessus before 2.0.6, in libnessus and possibly libnasl, a different set of vulnerabilities than those id (critical 10.0)
- [CVE-2003-0372](https://insights.sbomify.com/CVE-2003-0372/): Integer overflow in n/a (medium 4.6)
- [CVE-2003-0373](https://insights.sbomify.com/CVE-2003-0373/): Memory corruption in n/a (medium 4.4)
- [CVE-2007-3546](https://insights.sbomify.com/CVE-2007-3546/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2004-1445](https://insights.sbomify.com/CVE-2004-1445/): Race condition in n/a (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2722 is a low-severity vulnerability in n/a, published on 6 Oct 2007. 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-2004-2722 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-2722/ (Markdown: https://insights.sbomify.com/CVE-2004-2722/index.md)
```

## Sources

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

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