dbcve.org
FirepassHardware / appliance · F5

CVE-2007-0187

HIGH · 7.5 CVSS v2.0 Published 2007-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
F5 FirePass 5.4 through 5.5.2 and 6.0 allows remote attackers to access restricted URLs via (1) a trailing null byte, (2) multiple leading slashes, (3) Unicode encoding, (4) URL-encoded directory traversal or same-directory characters, or (5) upper case letters in the domain name.

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

F5 FirePass VPN controllers versions 5.4 through 5.5.2 and 6.0 contain a path traversal and URL access control bypass vulnerability. Attackers can bypass URL restrictions and access restricted resources by using various encoding techniques including trailing null bytes, multiple leading slashes, Unicode encoding, URL-encoded directory traversal sequences, or uppercase letters in the domain name.

MitigationApply vendor-supplied patches or upgrade to a patched version of F5 FirePass. As an interim control, implement web application firewall rules to filter requests containing these encoding patterns before they reach the FirePass device.

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
FirepassHardware / appliance
Affected:= 5.4= 5.4.1= 5.4.2= 5.4.3= 5.4.4= 5.4.5= 5.4.6= 5.4.7= 5.4.8= 5.4.9= 5.5= 5.5.1

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. Confirm F5 FirePass VPN deployment
    Identify if F5 FirePass VPN controllers are present in the environment by reviewing network documentation, asset inventory, or by checking for FirePass-related processes, services, or SSL VPN endpoints.
    Affected if F5 FirePass VPN controllers are deployed in the environment.
  2. Check FirePass version
    Access the FirePass administrative interface or use the command line to determine the installed version. Typically found in the system information page or via 'tmsh show sys version' command on the device.
    Affected if The installed version is 5.4, 5.4.1, 5.4.2, 5.4.3, 5.4.4, 5.4.5, 5.4.6, 5.4.7, 5.4.8, 5.4.9, 5.5, 5.5.1, or any version between 5.4 and 5.5.2 inclusive.
  3. Review URL access control configuration
    Examine the FirePass URL access control policies or restriction rules configured in the VPN to determine if restricted resources or administrative URLs are being protected.
    Affected if URL access control restrictions are defined for specific resources or paths on the FirePass device.
  4. Verify encoding-based bypass exposure
    Test or inspect web traffic logs for requests containing the bypass patterns: trailing null bytes, multiple leading slashes (e.g., ///), Unicode/UTF-8 encoding, URL-encoded sequences (e.g., %2e%2e), or uppercase letters in the host domain targeting restricted resources.
    Affected if Requests with these encoding patterns can reach the FirePass device and access resources that should be restricted by URL access controls.

The environment is affected if F5 FirePass versions 5.4 through 5.5.2 are deployed with URL access control restrictions that could be bypassed using encoding techniques.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or upgrade to a patched version of F5 FirePass. As an interim control, implement web application firewall rules to filter requests containing these encoding patterns before they reach the FirePass device.

Fix this in Firepass Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0187 — 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-2007-0187 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