# CVE-2008-6830: Auth bypass in n/a

> Attackers with valid credentials and browser access can hijack Citrix Web Interface sessions due to improper session termination.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7gq8-rx89-j29p

## What is CVE-2008-6830?

CVE-2008-6830 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Jun 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The disconnection feature in Citrix Web Interface 5.0 and 5.0.1 for Java Application Servers does not properly terminate a user's web interface session, which allows attackers with access to the same browser instance to gain access to the user's Web Interface session. NOTE: the attacker must also have valid credentials to the Web Interface.

## Which versions are affected by CVE-2008-6830?

It affects 1 product.


Products: Citrix Web Interface.

## How do I fix CVE-2008-6830?

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

## Is CVE-2008-6830 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4515](https://insights.sbomify.com/CVE-2010-4515/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-2454](https://insights.sbomify.com/CVE-2009-2454/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2007-6477](https://insights.sbomify.com/CVE-2007-6477/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6830 and fix it if it is affected.

What it is: CVE-2008-6830 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Jun 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-6830 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-2008-6830/ (Markdown: https://insights.sbomify.com/CVE-2008-6830/index.md)
```

## Sources

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

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