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

> Remote attackers can bypass authentication for the remote administration feature by using a URL with an extra leading slash.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-72pr-qpg4-f6xj

## What is CVE-2004-1695?

CVE-2004-1695 is a critical authentication bypass vulnerability in n/a, published on 20 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EmuLive Server4 Commerce Edition Build 7560 allows remote attackers to bypass authentication for the remote administration feature via a URL that contains an extra leading / (slash).

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

It affects 1 product.


Products: Emulive Server4.

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

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

## Is CVE-2004-1695 being exploited?

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

Public exploit code:

- EmuLive Server4 - Authentication Bypass / Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1696](https://insights.sbomify.com/CVE-2004-1696/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1695 is a critical authentication bypass vulnerability in n/a, published on 20 Feb 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-1695 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-1695/ (Markdown: https://insights.sbomify.com/CVE-2004-1695/index.md)
```

## Sources

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

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