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

> Remote attackers can bypass authentication by setting a specific HTTP parameter, potentially leading to unauthorized access and directory traversal.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 10 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-493f-4jww-99vv

## What is CVE-2008-0210?

CVE-2008-0210 is a medium-severity authentication bypass vulnerability in n/a, published on 10 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Uebimiau Webmail 2.7.10 and 2.7.2 does not protect authentication state variables from being set through HTTP requests, which allows remote attackers to bypass authentication via a sess[auth]=1 parameter settting.  NOTE: this can be leveraged to conduct directory traversal attacks without authentication by using CVE-2008-0140.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Uebimiau Webmail.

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

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

## Is CVE-2008-0210 being exploited?

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

Public exploit code:

- Uebimiau Web-Mail 2.7.10/2.7.2 - Remote File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-0140](https://insights.sbomify.com/CVE-2008-0140/): Path traversal in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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