# CVE-2009-4845: Hardcoded credentials in n/a

> Remote attackers can read cleartext SSH credentials from the configuration page, leading to unauthorized access and data exposure.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cw7x-73mr-gff9

## What is CVE-2009-4845?

CVE-2009-4845 is a medium-severity vulnerability in n/a, published on 7 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The configuration page in ToutVirtual VirtualIQ Pro 3.2 build 7882 contains cleartext SSH credentials, which allows remote attackers to obtain sensitive information by reading the username and password fields.

Weakness: CWE-310

## Which versions are affected by CVE-2009-4845?

It affects 1 product.


Products: Toutvirtual Virtualiq.

## How do I fix CVE-2009-4845?

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

## Is CVE-2009-4845 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4843](https://insights.sbomify.com/CVE-2009-4843/): Missing authorization in n/a (high 7.5)
- [CVE-2009-4849](https://insights.sbomify.com/CVE-2009-4849/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2009-4844](https://insights.sbomify.com/CVE-2009-4844/): Information disclosure in n/a (medium 5.0)
- [CVE-2009-4842](https://insights.sbomify.com/CVE-2009-4842/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-4848](https://insights.sbomify.com/CVE-2009-4848/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4845 and fix it if it is affected.

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

## Sources

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

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