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

> Remote attackers can hijack user sessions in Mantis because the session cookie is not cleared upon logout, allowing unauthorized access to user accounts.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g5wc-m94r-q66m

## What is CVE-2008-4689?

CVE-2008-4689 is a high-severity authentication bypass vulnerability in n/a, published on 22 Oct 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mantis before 1.1.3 does not unset the session cookie during logout, which makes it easier for remote attackers to hijack sessions.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Mantis Mantis.

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

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

## Is CVE-2008-4689 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6515](https://insights.sbomify.com/CVE-2006-6515/): Missing authorization in n/a (critical 10.0)
- [CVE-2006-0665](https://insights.sbomify.com/CVE-2006-0665/): Other in n/a (critical 10.0)
- [CVE-2002-1110](https://insights.sbomify.com/CVE-2002-1110/): SQL injection in n/a (critical 10.0)
- [CVE-2008-4687](https://insights.sbomify.com/CVE-2008-4687/): Code injection in n/a (critical 9.0)
- [CVE-2008-3333](https://insights.sbomify.com/CVE-2008-3333/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4689 is a high-severity authentication bypass vulnerability in n/a, published on 22 Oct 2008. 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-4689 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-4689/ (Markdown: https://insights.sbomify.com/CVE-2008-4689/index.md)
```

## Sources

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

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