发布时间 :2004-12-31 00:00:00
修订时间 :2017-07-10 21:31:58

[原文]clogin.php in Benchmark Designs' WHM AutoPilot 2.4.5 and earlier allows remote attackers to obtain plaintext username and password credentials by using the clogin_e and base64_encode functions to encode the desired user ID in the c parameter, then read the plaintext values in the resulting form.

[CNNVD]WHM AutoPilot Clogin.PHP用户名/密码信息泄露漏洞(CNNVD-200412-944)

        Benchmark Designs' WHM AutoPilot 2.4.5版本及之前版本的clogin.php存在漏洞。远程攻击者可以通过在c参数中使用clogin_e和base64_encode函数去编码期望的用户ID,来获得明文用户名和密码,然后在生成的表格中读取明文值。

- CVSS (基础分值)

CVSS分值: 5 [中等(MEDIUM)]
机密性影响: [--]
完整性影响: [--]
可用性影响: [--]
攻击复杂度: [--]
攻击向量: [--]
身份认证: [--]

- CPE (受影响的平台与产品)


- OVAL (用于检测的技术细节)


- 官方数据库链接
(官方数据源) MITRE
(官方数据源) NVD
(官方数据源) CNNVD

- 其它链接及资源
(VENDOR_ADVISORY)  FULLDISC  20040802 Benchmark Designs' WHM Autopilot backdoor vulnerability to plain-text password.
(UNKNOWN)  BID  10846
(UNKNOWN)  XF  whmautopilot-clogin-gain-access(16849)

- 漏洞信息

WHM AutoPilot Clogin.PHP用户名/密码信息泄露漏洞
中危 未知
2004-12-31 00:00:00 2005-12-01 00:00:00
        Benchmark Designs' WHM AutoPilot 2.4.5版本及之前版本的clogin.php存在漏洞。远程攻击者可以通过在c参数中使用clogin_e和base64_encode函数去编码期望的用户ID,来获得明文用户名和密码,然后在生成的表格中读取明文值。

- 公告与补丁

        Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: .

- 漏洞信息

WHM AutoPilot clogin.php Username/Password Disclosure
Remote / Network Access Authentication Management
Loss of Confidentiality
Exploit Public

- 漏洞描述

WHM AutoPilot contains a flaw that may lead to an unauthorized information disclosure.  The issue is due to an error in client login page "clogin.php". By calculating the hash value of user ID with "clogin_e()" and sending a specially crafted URI with the hash to the "c" parameter in "clogin.php" script, a remote attacker can retrive the username and password in plaintext, which will result in a loss of confidentiality.

- 时间线

2004-08-02 Unknow
2004-08-02 Unknow

- 解决方案

Currently, there are no known upgrades or patches to correct this issue. It is possible to correct the flaw by implementing the following workaround(s): Restrict access using .htaccess or similar to limit the exposure.

- 相关参考

- 漏洞作者