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

> Attackers can steal session IDs from logs or history due to insecure HTTP redirection in IBM Rational Build Forge.

- **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 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4g88-pvpj-755p

## What is CVE-2011-1839?

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

### Official description

IBM Rational Build Forge 7.1.0 uses the HTTP GET method during redirection from the authentication servlet to a PHP script, which makes it easier for context-dependent attackers to discover session IDs by reading (1) web-server access logs, (2) web-server Referer logs, or (3) the browser history.

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

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

It affects 1 product.


Products: Ibm Rational Build Forge.

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

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

## Is CVE-2011-1839 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2122](https://insights.sbomify.com/CVE-2008-2122/): Denial of service in n/a (high 7.5)
- [CVE-2011-1034](https://insights.sbomify.com/CVE-2011-1034/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2011-3391](https://insights.sbomify.com/CVE-2011-3391/): Missing authorization in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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