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

> Remote attackers can bypass authentication and gain privileges in Rantx by manipulating the logininfo cookie.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qw95-2v38-2pp5

## What is CVE-2008-2297?

CVE-2008-2297 is a high-severity authentication bypass vulnerability in n/a, published on 18 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The admin.php file in Rantx allows remote attackers to bypass authentication and gain privileges by setting the logininfo cookie to "<?php" or "?>", which is present in the password file and probably passes an insufficient comparison.

Weakness: CWE-264

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

It affects 1 product.


Products: Roticv Rantx.

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

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

## Is CVE-2008-2297 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2297 exists.

Public exploit code:

- RantX 1.0 - Insecure Admin Authentication (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2297 is a high-severity authentication bypass vulnerability in n/a, published on 18 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2297 exists.

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-2297/ (Markdown: https://insights.sbomify.com/CVE-2008-2297/index.md)
```

## Sources

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

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