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

> Remote attackers can obtain user credentials by directly requesting a sensitive include file stored under the web root with insufficient access control.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q3cv-q2hc-j88r

## What is CVE-2009-4096?

CVE-2009-4096 is a high-severity vulnerability in n/a, published on 28 Nov 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RADIO istek scripti 2.5 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain user credentials via a direct request for estafresgaftesantusyan.inc.

Weakness: CWE-255

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

It affects 1 product.


Products: Scriptlerim Radio Isetek Scripti.

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

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

## Is CVE-2009-4096 being exploited?

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

Public exploit code:

- Radio istek scripti 2.5 - Remote Configuration Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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