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

> Remote attackers can bypass the URL blocker on FortiGate devices by sending malformed HTTP requests, allowing 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:** 14 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h9mr-6gjh-qmfh

## What is CVE-2005-3058?

CVE-2005-3058 is a high-severity vulnerability in Fortinet Fortios, published on 14 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Interpretation conflict in Fortinet FortiGate 2.8, running FortiOS 2.8MR10 and v3beta, allows remote attackers to bypass the URL blocker via an (1) HTTP request terminated with a line feed (LF) and not carriage return line feed (CRLF) or (2) HTTP request with no Host field, which is still processed by most web servers without violating RFC2616.

Weakness: CWE-264

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

It affects 2 products.


Products: Fortinet Fortigate, Fortinet Fortios.

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

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

## Is CVE-2005-3058 being exploited?

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

Public exploit code:

- Fortinet Fortigate 2.x/3.0 - URL Filtering Bypass (exploitdb)

## Other vulnerabilities in Fortinet Fortios

- [CVE-2005-3057](https://insights.sbomify.com/CVE-2005-3057/): Security feature bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3058 is a high-severity vulnerability in Fortinet Fortios, published on 14 Feb 2006. 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-2005-3058 exists.

Affected product: Fortinet Fortios. 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-3058/ (Markdown: https://insights.sbomify.com/CVE-2005-3058/index.md)
```

## Sources

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

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