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

> Remote attackers can obtain sensitive customer data via session-related vectors in the admin customer search function.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v9wg-hp7h-x7f9

## What is CVE-2009-4236?

CVE-2009-4236 is a medium-severity vulnerability in n/a, published on 8 Dec 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The process function in data/class/pages/admin/customer/LC_Page_Admin_Customer_SearchCustomer.php in EC-CUBE Ver2 2.4.0 RC1 through 2.4.1, and Community Edition r18068 through r18428, allows remote attackers to obtain sensitive information (customer data) via unknown vectors related to sessions.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Ec-Cube Ec-Cube Ver2.

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

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

## Is CVE-2009-4236 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4236 is a medium-severity vulnerability in n/a, published on 8 Dec 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-4236 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-4236/ (Markdown: https://insights.sbomify.com/CVE-2009-4236/index.md)
```

## Sources

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

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