dbcve.org
Firepass 4100Hardware / appliance · F5

CVE-2007-0186

MEDIUM · 6.8 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 →
77/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
Multiple cross-site scripting (XSS) vulnerabilities in F5 FirePass SSL VPN allow remote attackers to inject arbitrary web script or HTML via (1) the xcho parameter to my.logon.php3; the (2) topblue, (3) midblue, (4) wtopblue, and certain other Custom color parameters in a per action to vdesk/admincon/index.php; the (5) h321, (6) h311, (7) h312, and certain other Front Door custom text color parameters in a per action to vdesk/admincon/index.php; the (8) ua parameter in a bro action to vdesk/admincon/index.php; the (9) app_param and (10) app_name parameters to webyfiers.php; (11) double eval functions; (12) JavaScript contained in an <FP_DO_NOT_TOUCH> element; and (13) the vhost parameter to my.activation.php. NOTE: it is possible that this candidate overlaps CVE-2006-3550.

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

Multiple cross-site scripting (XSS) vulnerabilities in F5 FirePass SSL VPN allow remote attackers to inject arbitrary web script or HTML via numerous parameters across multiple PHP files including my.logon.php3, vdesk/admincon/index.php, webyfiers.php, and my.activation.php. The vulnerabilities stem from insufficient input validation on color parameters, custom text parameters, the ua parameter, app_param, app_name, and the vhost parameter.

MitigationImplement robust input validation and proper output encoding for all user-supplied parameters across the affected PHP files. Additionally, check for and apply any available F5 FirePass firmware updates or security patches addressing this and potentially overlapping CVE-2006-3550.

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
Firepass 4100Hardware / appliance
Affected:all versions

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 4100 hardware model
    Access the FirePass administrative interface or check hardware labeling to verify the device model is FirePass 4100
    Affected if The device is an F5 FirePass 4100 unit (all versions affected)
  2. Check FirePass firmware version
    Navigate to the FirePass management console, typically at /my.saved_state.php or /my.diagnostics.php, to view the installed firmware version
    Affected if Any firmware version running on the FirePass 4100 hardware is affected since the advisory covers all versions
  3. Identify vulnerable PHP endpoints
    Check the HTTP server for the presence of the affected PHP files: my.logon.php3, vdesk/admincon/index.php, webyfiers.php, and my.activation.php
    Affected if These PHP files are accessible on the FirePass SSL VPN device
  4. Test for vulnerable parameters in URLs
    Attempt to access the known vulnerable endpoints with XSS test payloads in parameters: color, custom text, ua, app_param, app_name, vhost (for example: ?color=%3Cscript%3Ealert(1)%3C/script%3E)
    Affected if The application accepts and reflects unsanitized input in these parameters without proper HTML encoding
  5. Review web access logs for exploitation attempts
    Examine HTTP access logs for patterns containing script tags or HTML in the known vulnerable parameters (ua, app_param, app_name, vhost, color)
    Affected if Logs show attempts to inject HTML/script content into these specific parameters targeting the affected PHP files

If the environment contains an F5 FirePass 4100 device running any firmware version with the affected PHP files accessible, it is vulnerable to CVE-2007-0186 XSS attacks.

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

Implement robust input validation and proper output encoding for all user-supplied parameters across the affected PHP files. Additionally, check for and apply any available F5 FirePass firmware updates or security patches addressing this and potentially overlapping CVE-2006-3550.

Fix this in Firepass 4100 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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