# CVE-2005-4550: Path traversal in n/a

> Remote attackers can read arbitrary JSP and source files via null byte injection in the Discussion Forum Portlet.

- **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:** 28 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3hh7-4gv3-gf58

## What is CVE-2005-4550?

CVE-2005-4550 is a medium-severity path traversal vulnerability in n/a, published on 28 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PORTAL schema in Oracle Application Server (OracleAS) Discussion Forum Portlet allows remote attackers to obtain the source code for arbitrary JSP and other files via a df_next_page parameter with a trailing null byte (%00).

## Which versions are affected by CVE-2005-4550?

It affects 1 product.


Products: Oracle Application Server Discussion Forum Portlet.

## How do I fix CVE-2005-4550?

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

## Is CVE-2005-4550 being exploited?

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

Public exploit code:

- oracle Application server discussion forum portlet - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4549](https://insights.sbomify.com/CVE-2005-4549/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4550 and fix it if it is affected.

What it is: CVE-2005-4550 is a medium-severity path traversal vulnerability in n/a, published on 28 Dec 2005. 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-2005-4550 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-2005-4550/ (Markdown: https://insights.sbomify.com/CVE-2005-4550/index.md)
```

## Sources

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

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