# CVE-2010-2336: Information disclosure in n/a

> Remote attackers can obtain source code of executable files in the web root via the download parameter in Yamamah Photo Gallery.

- **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:** 18 Jun 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pq4m-gxfg-5hgm

## What is CVE-2010-2336?

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

### Official description

index.php in Yamamah Photo Gallery 1.00 allows remote attackers to obtain the source code of executable files within the web document root via the download parameter.

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

## Which versions are affected by CVE-2010-2336?

It affects 1 product.


Products: Yamamah Yamamah.

## How do I fix CVE-2010-2336?

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

## Is CVE-2010-2336 being exploited?

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

Public exploit code:

- Yamamah - 'news' SQL Injection / Source Code Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-2335](https://insights.sbomify.com/CVE-2010-2335/): SQL injection in n/a (high 7.5)
- [CVE-2010-1300](https://insights.sbomify.com/CVE-2010-1300/): SQL injection in n/a (high 7.5)
- [CVE-2011-3823](https://insights.sbomify.com/CVE-2011-3823/): Information disclosure in n/a (medium 5.0)
- [CVE-2010-2334](https://insights.sbomify.com/CVE-2010-2334/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2336 and fix it if it is affected.

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

## Sources

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

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