dbcve.org
FortiosOperating system · Fortinet

CVE-2005-3058

HIGH · 7.5 CVSS v2.0 Published 2005-12-31
Fix available
A fix is available. Upgrade to after 3_beta or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Fortinet FortiGate 2.8 running FortiOS 2.8MR10 and v3beta contains an interpretation conflict in its URL blocking feature. Attackers can bypass the URL blocker by sending HTTP requests terminated with a Line Feed (LF) instead of the standard Carriage Return Line Feed (CRLF), or by omitting the Host field entirely. These non-RFC2616-compliant requests bypass the FortiGate's filter but are still processed by backend web servers.

MitigationUpgrade FortiOS to a patched version beyond 2.8MR10/v3beta. If the hardware cannot support a current FortiOS version, consider network-level HTTP filtering or replacing the end-of-life device with a supported model.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortiosOperating system
Affected:<= 2.8_mr10<= 3_beta
FortigateHardware / appliance
Affected:= 2.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the FortiOS version
    Log into the FortiGate CLI and run the command 'get system status' or 'show system global' to view the firmware version. Alternatively, access the web UI under System > Status to see the FortiOS version.
    Affected if The version displayed is 2.8MR10 or below, or 3.0beta (any version listed as <= 2.8_mr10 or <= 3_beta in the affected ranges).
  2. Confirm the URL filtering feature is active
    In the FortiGate web UI, navigate to Firewall > URL Filter or Security Profiles > URL Filtering to verify if any URL blocking rules are configured and enabled.
    Affected if URL filtering is enabled and configured with blocking rules, as the bypass affects the protection provided by this feature.
  3. Check HTTP proxy or inspection mode configuration
    In the CLI, run 'get webfilter profile' or 'show webfilter' to review the web filter profiles. Also check if the device is operating in proxy-based or flow-based inspection mode using 'get system global | grep proxy'.
    Affected if The device is using proxy-mode HTTP inspection, as this interpretation conflict occurs when the FortiGate parses HTTP requests before forwarding them.
  4. Inspect HTTP traffic handling for non-standard requests
    Review any available traffic logs or packet captures for requests using LF (0x0A) line endings instead of CRLF (0x0D0A), or HTTP requests that lack a Host header field. Enable debug logging with 'diagnose debug application urlfilter 7' if available.
    Affected if Traffic logs show requests reaching backend servers that the URL filter should have blocked, indicating the bypass is being exploited.

You are affected if your FortiGate runs FortiOS 2.8MR10 or below (or 3.0beta) AND has URL filtering enabled, as the non-RFC2616-compliant HTTP requests can bypass your URL blocking rules.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 3_beta
Interim mitigation

Upgrade FortiOS to a patched version beyond 2.8MR10/v3beta. If the hardware cannot support a current FortiOS version, consider network-level HTTP filtering or replacing the end-of-life device with a supported model.

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-3058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-3058 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data