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

> Remote attackers can hijack sessions and access sensitive analysis data due to predictable session IDs in CGI Cafe Access Analyzer.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 2 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9v9f-xp6r-cmh2

## What is CVE-2008-5809?

CVE-2008-5809 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

futomi CGI Cafe Access Analyzer CGI Standard 4.0.1 and earlier and Access Analyzer CGI Professional 4.11.3 and earlier use a predictable session id, which makes it easier for remote attackers to hijack sessions, and obtain sensitive information about analysis results, via a modified id.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Futomi Access Analyzer Cgi.

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

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

## Is CVE-2008-5809 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2366](https://insights.sbomify.com/CVE-2010-2366/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-0971](https://insights.sbomify.com/CVE-2009-0971/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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