Weak Password Policy

Vendor of the product(s): Rubicon Communications, LLC (Netgate).

Product Name:Netgate 

Vendor Mail –ID: [email protected]

 

Version – exact ver of the product which is vulnerable: Pfsense firewall version 2.6.0 CE

 

Affected component(s) :Password change functionalities
 

Attack vector(s):NA
 

Suggested description of the vulnerability for use in the

CVE :Lack of password policy in Pfsense CE

Discoverer(s)/Credits – :Dipendar Sharma
 

Overview:- 

All Pfsense CE,  does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. 

Details :- 

CWE-521: Weak Password Requirements 

Authentication mechanisms often rely on a memorized secret (also known as a password) to provide an assertion of identity for a user of a system. It is therefore important that this password be of sufficient complexity and impractical for an adversary to guess. The specific requirements around how complex a password needs to be depends on the type of system being protected. Selecting the correct password requirements and enforcing them through implementation are critical to the overall success of the authentication mechanism. 

Poc Details:- 

Login to the application as admin:pfsense via visiting http://10.118.20.200/system_usermanager.php?act=edit&userid=2  

Step-1 Click on system>user manager>users and attacker can change any user password

Step-2 Enter new password any example :123  

 

Step-3 Click on save and logout your account  

Step-4 Login with new password username:admin password:123 

Affected Environments 

Pfsense CE all version  

Prevention 

A product’s design should require adherence to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes: 

Enforcement of a minimum and maximum length 

Restrictions against password reuse 

Restrictions against using common passwords 

Restrictions against using contextual string in the password (e.g., user id, app name) 

Depending on the threat model, the password policy may include several additional attributes. 

Complex passwords requiring mixed character sets (alpha, numeric, special, mixed case) 

Increasing the range of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication. 

Unfortunately, a complex password may be difficult to memorize, encouraging a user to select a short password or to incorrectly manage the password (write it down). 

Another disadvantage of this approach is that it often does not result in a significant increases in overal password complexity due to people’s predictable usage of various symbols. 

Large Minimum Length (encouraging passphrases instead of passwords) 

Increasing the number of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication. 

A disadvantage of this approach is that selecting a good passphrase is not easy and poor passwords can still be generated. Some prompting may be needed to encourage long un-predictable passwords. 

Randomly Chosen Secrets 

Generating a password for the user can help make sure that length and complexity requirements are met, and can result in secure passwords being used. 

A disadvantage of this approach is that the resulting password or passpharse may be too difficult to memorize, encouraging them to be written down. 

Password Expiration 

Requiring a periodic password change can reduce the time window that an adversary has to crack a password, while also limiting the damage caused by password exposures at other locations. 

Password expiration may be a good mitigating technique when long complex passwords are not desired.