Qpopper username brute force
| qpopper-username-bruteforce (11543) |  Medium Risk |
Description:
Qualcomm Qpopper could allow a remote attacker to determine Qpopper usernames. If a user attempts to connect to the mail server with a valid username and an invalid password, the mail server waits approximately 10 seconds before disconnecting. However, if a user attempts to connect with an invalid username and password, the mail server would disconnect immediately after the authentication credentials are supplied. This could allow a remote attacker to use brute force techniques to determine a valid username.
Consequences:
Bypass Security
Remedy:
For OpenPKG:
Upgrade to the latest qpopper package as listed below. Refer to OpenPKG Security Advisory OpenPKG-SA-2003.018 for more information. See References.
OpenPKG CURRENT: 4.0.5-20030313 or later
OpenPKG 1.2: 4.0.4-1.2.1 or later
OpenPKG 1.1: 4.0.4-1.1.2 or later
References:
- BugTraq Mailing List, Sat Mar 15 2003 - 13:13:43 CST : qpopper timing analysis on to determine if a username exists on a system.
- BugTraq Mailing List, Wed Jun 18 2003 - 13:43:44 CDT : Qpopper leaks information during authentication.
- BugTraq Mailing List, Wed Jun 18 2003 - 15:09:15 CDT: Re: ConnecTalk Security Advisory: Qpopper leaks information during authentication.
- Qualcomm Web site: Qpopper Home Page.
- Qualcomm Web site: Qpopper Home Page.
- BID-7110: Qpopper Username Information Disclosure Weakness
Platforms Affected:
- OpenPKG OpenPKG 1.1
- OpenPKG OpenPKG 1.2
- OpenPKG OpenPKG CURRENT
- Qualcomm Qpopper 4.0.4
- Qualcomm Qpopper 4.0.5
Reported:
Mar 15, 2003
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this