# CVE-2004-1878: Auth bypass in n/a

> Remote attackers can bypass authentication and access sensitive data by sending a direct request with double leading slashes to the admin user script.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3h5c-58g7-j245

## What is CVE-2004-1878?

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

### Official description

LINBOX LIN:BOX allows remote attackers to bypass authentication, obtain sensitive information, or gain access via a direct request to admin/user.pl preceded by // (double leading slash).

## Which versions are affected by CVE-2004-1878?

It affects 1 product.


Products: Linbit Technologies Linbox Officeserver.

## How do I fix CVE-2004-1878?

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

## Is CVE-2004-1878 being exploited?

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

Public exploit code:

- LinBit Technologies LINBOX Officeserver - Remote Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1878 and fix it if it is affected.

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

## Sources

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

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