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

> Remote attackers can enumerate valid user accounts configured for One-Time Passwords via OpenSSH PAM integration, revealing account existence.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** Yes
- **Published:** 21 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** AZL-35079, AZL-6778, DEBIAN-CVE-2007-2768, GHSA-7c33-39g7-9rjm

## What is CVE-2007-2768?

CVE-2007-2768 is a medium-severity vulnerability in Netapp Hci Management Node, published on 21 May 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSSH, when using OPIE (One-Time Passwords in Everything) for PAM, allows remote attackers to determine the existence of certain user accounts, which displays a different response if the user account exists and is configured to use one-time passwords (OTP), a similar issue to CVE-2007-2243.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 5 products.


Products: Netapp Hci Management Node, Netapp Hci Storage Node, Netapp Solidfire, Netapp Steelstore Cloud Integrated Storage, OpenSSH.

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

Apply the vendor's patch.

## Is CVE-2007-2768 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2768 is a medium-severity vulnerability in Netapp Hci Management Node, published on 21 May 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-2768 in the wild and no public exploit code.

Affected product: Netapp Hci Management Node. 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-2768/ (Markdown: https://insights.sbomify.com/CVE-2007-2768/index.md)
```

## Sources

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

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