CVE-2005-3058 json
Interpretation conflict in Fortinet FortiGate 2.8, running FortiOS 2.8MR10 and v3beta, allows remote attackers to bypass the URL blocker vi…
published 20y ago modified 4mo ago also EUVD-2005-3058
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
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.
Is CVE-2005-3058 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-27203)
Exploit prediction
3.09% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-27203 Fortinet Fortigate 2.x/3.0 - URL Filtering Bypass remote, 2006-02-13
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
secunia.com
/advisories/18844
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2006/0539
vdb-entry, vendor-advisory
-
lists.grok.org.uk
/pipermail/full-disclosure/2006-February/042140.html
mailing-list
-
securityfocus.com
/archive/1/424858/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24626
vdb-entry
-
securityfocus.com
/bid/16599
vdb-entry
- fortiguard.com /advisory/FGA-2006-10.html
Sources
- CVE List CVE-2005-3058
- NVD CVE-2005-3058
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.