# CVE-2000-0241: Information disclosure in n/a

> Attackers can read cleartext passwords from the server configuration file to gain unauthorized privileges on vqSoft vqServer.

- **Severity:** Medium 5.0 (`AV:N/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:** 12 Apr 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q9jx-r63x-g7f5

## What is CVE-2000-0241?

CVE-2000-0241 is a medium-severity vulnerability in n/a, published on 12 Apr 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

vqSoft vqServer stores sensitive information such as passwords in cleartext in the server.cfg file, which allows attackers to gain privileges.

## Which versions are affected by CVE-2000-0241?

It affects 1 product.


Products: Vqsoft Vqserver.

## How do I fix CVE-2000-0241?

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

## Is CVE-2000-0241 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0731](https://insights.sbomify.com/CVE-2002-0731/): Cross-site scripting in n/a (high 7.5)
- [CVE-2000-0766](https://insights.sbomify.com/CVE-2000-0766/): Memory corruption in n/a (high 7.5)
- [CVE-2000-0240](https://insights.sbomify.com/CVE-2000-0240/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0241 and fix it if it is affected.

What it is: CVE-2000-0241 is a medium-severity vulnerability in n/a, published on 12 Apr 2000. 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-2000-0241 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-2000-0241/ (Markdown: https://insights.sbomify.com/CVE-2000-0241/index.md)
```

## Sources

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

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