# CVE-2009-2022: Information disclosure in n/a

> Remote attackers can download the database file via direct request to obtain sensitive information due to insufficient access control.

- **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:** 9 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j3jp-46wx-ch5m

## What is CVE-2009-2022?

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

### Official description

fipsCMS Light 2.1 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download the database file and obtain sensitive information via a direct request for _fipsdb/db.mdb.

Weakness: CWE-264

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

It affects 1 product.


Products: Fipsasp Fipscms Light.

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

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

## Is CVE-2009-2022 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2022 exists.

Public exploit code:

- FipsCMS Light 2.1 - 'db.mdb' Remote Database Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3417](https://insights.sbomify.com/CVE-2008-3417/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2022 is a medium-severity vulnerability in n/a, published on 9 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2022 exists.

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-2022/ (Markdown: https://insights.sbomify.com/CVE-2009-2022/index.md)
```

## Sources

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

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