# CVE-2007-0195: Information disclosure in n/a

> Remote attackers can enumerate valid LDAP usernames by observing distinct error messages during failed login attempts on F5 FirePass.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w5v6-gw7h-cxrj

## What is CVE-2007-0195?

CVE-2007-0195 is a medium-severity vulnerability in n/a, published on 11 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

my.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.

## Which versions are affected by CVE-2007-0195?

It affects 1 product.


Products: F5 Firepass.

## How do I fix CVE-2007-0195?

No fix has been published for CVE-2007-0195 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-0195 being exploited?

There is no known exploitation of CVE-2007-0195 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-1777](https://insights.sbomify.com/CVE-2012-1777/): SQL injection in n/a (high 7.5)
- [CVE-2007-0187](https://insights.sbomify.com/CVE-2007-0187/): Path traversal in n/a (high 7.5)
- [CVE-2012-2053](https://insights.sbomify.com/CVE-2012-2053/): Privilege escalation in n/a (high 7.2)
- [CVE-2007-0188](https://insights.sbomify.com/CVE-2007-0188/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0195 and fix it if it is affected.

What it is: CVE-2007-0195 is a medium-severity vulnerability in n/a, published on 11 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0195 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-0195/ (Markdown: https://insights.sbomify.com/CVE-2007-0195/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-0195
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-0195
- OSV: https://osv.dev/vulnerability/CVE-2007-0195

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-0195/
Summaries are generated and may contain mistakes; the official description above is the record.