# CVE-2005-1596: Auth bypass in n/a

> Remote attackers can bypass authentication and execute arbitrary code in Fusion SBX by manipulating specific parameters in index.php.

- **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:** 16 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f4hx-rjjx-8grw

## What is CVE-2005-1596?

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

### Official description

index.php in Fusion SBX 1.2 and earlier does not properly use the extract function, which allows remote attackers to bypass authentication by setting the is_logged parameter or execute arbitrary code via the maxname2 parameter.

## Which versions are affected by CVE-2005-1596?

It affects 1 product.


Products: Fusion Sbx.

## How do I fix CVE-2005-1596?

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

## Is CVE-2005-1596 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1596 and fix it if it is affected.

What it is: CVE-2005-1596 is a critical authentication bypass vulnerability in n/a, published on 16 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1596 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-2005-1596/ (Markdown: https://insights.sbomify.com/CVE-2005-1596/index.md)
```

## Sources

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

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