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

> Remote attackers can bypass authentication and gain administrator privileges on RaidSonic ICY BOX NAS devices by manipulating the login parameter.

- **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:** 25 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-236h-5c6c-jrfx

## What is CVE-2008-7081?

CVE-2008-7081 is a critical authentication bypass vulnerability in n/a, published on 25 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

userHandler.cgi in RaidSonic ICY BOX NAS firmware 2.3.2.IB.2.RS.1 allows remote attackers to bypass authentication and gain administrator privileges by setting the login parameter to admin. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Raidsonic Icy Box Nas.

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

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

## Is CVE-2008-7081 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7081 is a critical authentication bypass vulnerability in n/a, published on 25 Aug 2009. 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-2008-7081 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-2008-7081/ (Markdown: https://insights.sbomify.com/CVE-2008-7081/index.md)
```

## Sources

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

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