# CVE-2006-3487: Information disclosure in n/a

> Remote attackers can access the local database file directly due to insufficient access control, exposing sensitive information.

- **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:** 10 Jul 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pjw4-j8j8-vf48

## What is CVE-2006-3487?

CVE-2006-3487 is a medium-severity vulnerability in n/a, published on 10 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VirtuaStore 2.0 stores sensitive files under the web root with insufficient access control, which allows remote attackers to obtain local database information by directly accessing database/virtuastore.mdb.

## Which versions are affected by CVE-2006-3487?

It affects 1 product.


Products: Virtuastore Virtuastore.

## How do I fix CVE-2006-3487?

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

## Is CVE-2006-3487 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3402](https://insights.sbomify.com/CVE-2006-3402/): SQL injection in n/a (high 7.5)
- [CVE-2006-3488](https://insights.sbomify.com/CVE-2006-3488/): Absolute path traversal vulnerability in administrador.asp in VirtuaStore 2.0 allows remote attackers to possibly read arbitrary directories (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3487 and fix it if it is affected.

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

## Sources

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

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