# CVE-2006-1358: Information disclosure in n/a

> An attacker with a valid account can view another user's portlet content due to session cache errors in WebLogic 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:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gxxr-jv9h-5q3v

## What is CVE-2006-1358?

CVE-2006-1358 is a medium-severity vulnerability in n/a, published on 22 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in BEA WebLogic Portal 8.1 up to SP5 causes a JSR-168 Portlet to be retrieved from the cache for the wrong session, which might allow one user to see a Portlet of another user.

## Which versions are affected by CVE-2006-1358?

It affects 1 product.


Products: Oracle Weblogic Portal.

## How do I fix CVE-2006-1358?

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

## Is CVE-2006-1358 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0423](https://insights.sbomify.com/CVE-2006-0423/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2006-0428](https://insights.sbomify.com/CVE-2006-0428/): Missing authorization in n/a (high 7.5)
- [CVE-2007-0426](https://insights.sbomify.com/CVE-2007-0426/): Security feature bypass in n/a (medium 6.8)
- [CVE-2006-0425](https://insights.sbomify.com/CVE-2006-0425/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-2680](https://insights.sbomify.com/CVE-2005-2680/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1358 and fix it if it is affected.

What it is: CVE-2006-1358 is a medium-severity vulnerability in n/a, published on 22 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1358 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-2006-1358/ (Markdown: https://insights.sbomify.com/CVE-2006-1358/index.md)
```

## Sources

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

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