FirepassHardware / appliance · F5
CVE-2007-0195
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 · uneditedmy.activation.php3 in F5 FirePass 5.4 through 5.5.1 and 6.0 displays different error messages for failed login attempts with a valid username than for those with an invalid username, which allows remote attackers to confirm the validity of an LDAP account.
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 confidenceThe my.activation.php3 script in F5 FirePass 5.4-6.0 returns different error messages for failed authentication attempts depending on whether the supplied username exists in LDAP, allowing remote attackers to enumerate valid user accounts through repeated login attempts.
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
= 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.1CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check FirePass versionAccess the FirePass management interface or CLI and retrieve the installed version number. This is typically visible in the web UI header or via command line using 'tmsh show sys version' or similar F5 command.Affected if The installed version matches 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, or 5.5.1
-
Confirm my.activation.php3 existsAttempt to access the URL path /my.activation.php3 on the FirePass device via HTTP or HTTPS to verify the script is present.Affected if The script returns a response rather than a 404 Not Found error, indicating the vulnerable script is accessible on the device.
-
Test authentication error messagesSubmit two login attempts to the FirePass authentication endpoint using two different usernames: one that likely exists in the LDAP directory and one that does not. Capture the error message returned for each attempt.Affected if The error messages differ between the two attempts, with one indicating the user exists but credentials are wrong versus an invalid username message. This difference confirms the enumeration vulnerability.
-
Verify LDAP authentication is in useCheck the FirePass configuration to confirm that LDAP directory authentication is enabled as the user validation method.Affected if LDAP authentication is configured and the FirePass version is within the affected range listed above, the vulnerability is present.
The environment is affected if the FirePass version is 5.4 through 5.5.1, the my.activation.php3 script is accessible, and the login page returns different error messages for valid versus invalid usernames.
Generated from the published advisory. Verify against your own configuration.
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 dataConfigure the authentication system to return identical error messages regardless of username validity, or upgrade to a supported F5 product version as FirePass reached end-of-life.
Fix this in Firepass
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0195 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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