# CVE-2011-1569: Information disclosure in n/a

> Remote attackers can obtain source code of arbitrary files under the web root via specific parameter manipulations in Douran Portal.

- **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:** 5 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9hh8-jw9v-6483

## What is CVE-2011-1569?

CVE-2011-1569 is a medium-severity vulnerability in n/a, published on 5 Apr 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

download.aspx in Douran Portal 3.9.7.8 allows remote attackers to obtain source code of arbitrary files under the web root via (1) a trailing ".", (2) a trailing space, or (3) mixed case in the FileNameAttach parameter.

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

## Which versions are affected by CVE-2011-1569?

It affects 1 product.


Products: Douran Portal.

## How do I fix CVE-2011-1569?

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

## Is CVE-2011-1569 being exploited?

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

Public exploit code:

- Douran 3.9.7.8 - File Download/Source Code Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1569 and fix it if it is affected.

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

## Sources

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

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