# CVE-2005-0290: Security feature bypass in n/a

> Remote attackers can bypass security filters on NETGEAR FVS318 devices by using hex-encoded URLs, allowing unauthorized access to restricted content.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wqw3-8gp3-w5x9

## What is CVE-2005-0290?

CVE-2005-0290 is a high-severity vulnerability in n/a, published on 10 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETGEAR FVS318 running firmware 2.4, and possibly other versions, allows remote attackers to bypass the filters using hex encoded URLs, as demonstrated using a hex encoded file extension.

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

It affects 1 product.


Products: Netgear Fvs318.

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

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

## Is CVE-2005-0290 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0611](https://insights.sbomify.com/CVE-2004-0611/): Denial of service in n/a (medium 5.0)
- [CVE-2005-0291](https://insights.sbomify.com/CVE-2005-0291/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2002-1892](https://insights.sbomify.com/CVE-2002-1892/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0290 is a high-severity vulnerability in n/a, published on 10 Feb 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-0290 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-0290/ (Markdown: https://insights.sbomify.com/CVE-2005-0290/index.md)
```

## Sources

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

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