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

> Remote attackers can download the sensitive database file by directly requesting admin.mdb 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:** 27 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3wh5-4rmj-5jxh

## What is CVE-2009-2602?

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

### Official description

R2 Newsletter Lite, Pro, and Stats stores sensitive information under the web root with insufficient access control, which allows remote attackers to download the database file via a direct request for admin.mdb.

Weakness: CWE-264

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

It affects 3 products.


Products: R2newsletter R2 Newsletter Lite, R2newsletter R2 Newsletter Pro, R2newsletter R2 Newsletter Stats.

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

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

## Is CVE-2009-2602 being exploited?

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

Public exploit code:

- R2 NewsLetter Lite/Pro/Stats - 'admin.mdb' Database Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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