CVE-2007-2768
NoneCVSS
—
EPSS
8.6%
Published
May 21, 2007
CISA due date
—
Cloudanix analysis
A flaw in older SSH setups could let attackers figure out which user accounts exist on a system, making it easier for them to focus attacks on real users.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Moderate
- Impact
- Data Exposure
- Component
- Network Service
- Class
- Information Disclosure
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
The vulnerability allows remote attackers to enumerate valid user accounts by observing distinct responses during authentication attempts when OPIE is configured for PAM, revealing whether a user exists and uses one-time passwords.
Why it matters to the business
Attackers can identify valid accounts more easily, increasing the risk of targeted brute-force or password guessing attacks on systems using older OpenSSH configurations, potentially leading to unauthorized access over time.
How an attack unfolds
An attacker connects to the SSH service and initiates authentication with OPIE-enabled PAM, sending probes for potential usernames; the server responds differently for existing OTP-configured users versus non-existent ones, allowing enumeration.
How to fix it
Upgrade affected OpenSSH installations or Bitnami node packages to version 10.24.1 or later, and consider disabling OPIE if not required.
How to confirm the fix worked
Verify the OpenSSH version is updated and test authentication responses for non-existent users to ensure uniform error messages.
Typical attack path
- Connect to SSH port
- Attempt authentication with OPIE PAM for various usernames
- Analyze response differences to identify valid accounts
- Use enumerated accounts for further attacks like password spraying
How to detect it
Examine SSH authentication logs for patterns of failed login attempts targeting multiple usernames with similar timing, looking for response variations indicating account existence checks.
- OPIE PAM authentication probe patterns in sshd logs
- Repeated SSH connections from single source testing multiple usernames
What your security team should do
- Immediately upgrade to the fixed version 10.24.1
- Review PAM configurations to disable unnecessary OTP methods
- Monitor authentication logs for enumeration attempts
- Implement account lockout policies
The record
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.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:10 | openssh | 0 | No fix |
| Debian:11 | openssh | 0 | No fix |
| Debian:12 | openssh | 0 | No fix |
| Debian:13 | openssh | 0 | No fix |
Related vulnerabilities
- CVE-2023-51767 OpenSSH through 10.0, when common types of DRAM are used, might allow row hammer attacks… Also affects openssh
- CVE-2023-51385 In ssh in OpenSSH before 9.6, OS command injection might occur if a user name or host… Also affects openssh
- CVE-2021-36368 An issue was discovered in OpenSSH before 8.9. Also affects openssh
- CVE-2021-41617 sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are… Also affects openssh
- CVE-2016-20012 OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain… Also affects openssh
- CVE-2017-15906 The process_open function in sftp-server.c in OpenSSH before 7.6 does not properly… Also affects openssh
- CVE-2016-10011 authfile.c in sshd in OpenSSH before 7.4 does not properly consider the effects of… Also affects openssh
- CVE-2016-10012 The shared memory manager (associated with pre-authentication compression) in sshd in… Also affects openssh